0
我正在开发一个网站，我我是用数字海洋具有AWS溃败53AWS R53不解析名称
最初的问题，所以我成立了A记录到服务器的IP和更新了我的注册服务器域名服务器（godaddy）。 一切工作正常。
现在我托管在Heroku上，但它不解析名称。
如果我访问teamcomp.net，我正确地重定向到www.teamcomp.net，所以我认为S3存储桶配置正确。
但在那之后，火狐不能www.teamcomp.net找到服务器。
Server not found
Check the address for typing errors such as ww.example.com instead of www.example.com
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
我跟着指令在https://devcenter.heroku.com/articles/route-53，我添加所述结构域Heroku的应用程序和注册的名称服务器设置正确。
$ heroku domains
=== mysterious-reef-3637 Heroku Domain
mysterious-reef-3637.herokuapp.com
=== mysterious-reef-3637 Custom Domains
Domain Name DNS Target
──────────────── ──────────────────────────────────
www.teamcomp.net mysterious-reef-3637.herokuapp.com
teamcomp.net mysterious-reef-3637.herokuapp.com
这是我目前的配置。它看起来对我来说，我做的一切都像向导说，但我不能达到从该域的网站（它的工作原理，如果我使用Heroku的域）
$ host teamcomp.net
Host teamcomp.net not found: 2(SERVFAIL)
我能做些什么要解决这个问题？
其他相关信息
$ dig +recurse +trace teamcomp.net any
; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> +recurse +trace teamcomp.net any
;; global options: +cmd
. 304830 IN NS g.root-servers.net.
. 304830 IN NS h.root-servers.net.
. 304830 IN NS i.root-servers.net.
. 304830 IN NS j.root-servers.net.
. 304830 IN NS k.root-servers.net.
. 304830 IN NS l.root-servers.net.
. 304830 IN NS m.root-servers.net.
. 304830 IN NS a.root-servers.net.
. 304830 IN NS b.root-servers.net.
. 304830 IN NS c.root-servers.net.
. 304830 IN NS d.root-servers.net.
. 304830 IN NS e.root-servers.net.
. 304830 IN NS f.root-servers.net.
;; Received 755 bytes from 127.0.1.1#53(127.0.1.1) in 3393 ms
net. 172800 IN NS f.gtld-servers.net.
net. 172800 IN NS a.gtld-servers.net.
net. 172800 IN NS b.gtld-servers.net.
net. 172800 IN NS c.gtld-servers.net.
net. 172800 IN NS l.gtld-servers.net.
net. 172800 IN NS h.gtld-servers.net.
net. 172800 IN NS g.gtld-servers.net.
net. 172800 IN NS j.gtld-servers.net.
net. 172800 IN NS i.gtld-servers.net.
net. 172800 IN NS k.gtld-servers.net.
net. 172800 IN NS d.gtld-servers.net.
net. 172800 IN NS e.gtld-servers.net.
net. 172800 IN NS m.gtld-servers.net.
net. 86400 IN DS 35886 8 2 7862B27F5F516EBE19680444D4CE5E762981931842C465F00236401D 8BD973EE
net. 86400 IN RRSIG DS 8 1 86400 20151224170000 20151214160000 62530 . Kmd1EaxlpKS2T8PZIV/HWmZe8glRgOKjgtjfuvx4D4YDPGRnyOxWXVql 4Y8srSFmvDPDR382hMQWLaOwjnVCO4dMWPnRIoYvzqo05a2/7EOJDXlV 6WczFZKy+9M7oUj4XeeHrpi04ypUj/gXvnCMNKk3/5QJl4T8MovWEHeu hXw=
;; Received 733 bytes from 192.228.79.201#53(b.root-servers.net) in 7182 ms
teamcomp.net. 172800 IN NS ns-1351.awsdns-40.org.
teamcomp.net. 172800 IN NS ns-2043.awsdns-63.co.uk.
teamcomp.net. 172800 IN NS ns-210.awsdns-26.com.
teamcomp.net. 172800 IN NS ns-526.awsdns-01.net.
A1RT98BS5QGC9NFI51S9HCI47ULJG6JH.net. 86400 IN NSEC3 1 1 0 - A1RUUFFJKCT2Q54P78F8EJGJ8JBK7I8B NS SOA RRSIG DNSKEY NSEC3PARAM
A1RT98BS5QGC9NFI51S9HCI47ULJG6JH.net. 86400 IN RRSIG NSEC3 8 2 86400 20151218061702 20151211050702 37703 net. QEvwTsJgNbCEgO6sLxxz09CG5Ugs4hPXoRo+8W5o4Xn5nrkdN7lw0rNI DFS/C6dJtShsOkX2/0EIpp8DaGAvjgTs6jLu+oZzgTaedKHSk0cQUPVf EcGNbbpp8FCHz0yUMBes9FPg8WAe+DXNZ++lCjtK5aO89EEWJqNEOjfP vmA=
UC4NBKDSCVJ8ARDU0BVH1BBDDQ15GR8I.net. 86400 IN NSEC3 1 1 0 - UC518K8QR415HBJULMN8MLAPPT20CKR1 NS DS RRSIG
UC4NBKDSCVJ8ARDU0BVH1BBDDQ15GR8I.net. 86400 IN RRSIG NSEC3 8 2 86400 20151220062946 20151213051946 37703 net. Re7MIW4RzyQdlEfoIM1TrQIq8mG5VvLlGvDfba+NeUAbnKNZMmW+WCYr n3Jktc9xVXJoecBZg+CSTG03CWqG8GkA8RiQQjAVKF1dcWRph6mGLglM crgzBFvK4H+uo6WJDkOowm7jA736J/9/FWJ1GoBXMoFMvz/HmPiujpRR Hgs=
;; Received 695 bytes from 192.43.172.30#53(i.gtld-servers.net) in 548 ms
teamcomp.net. 5 IN A 54.231.131.76
teamcomp.net. 172800 IN NS ns-1351.awsdns-40.org.
teamcomp.net. 172800 IN NS ns-2043.awsdns-63.co.uk.
teamcomp.net. 172800 IN NS ns-210.awsdns-26.com.
teamcomp.net. 172800 IN NS ns-526.awsdns-01.net.
teamcomp.net. 900 IN SOA ns-210.awsdns-26.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
;; Received 255 bytes from 205.251.194.14#53(ns-526.awsdns-01.net) in 494 ms
现在，teamcomp.net和www.teamcomp.net都解决得很好，所以它可能是Route 53传播延迟。你有没有改变它来使它工作？ –
不，仍然是相同的配置。 我注意到，从我的手机它的工作，但我的电脑没有。 我的电脑是大学网络的背后，我想这是DNS花费很长的时间来更新字段。当我连接大学WiFi时，我的手机也无法访问该网站。 有没有办法确保这一点？ –
它可能是您的提供商不正确的DNS缓存。截图上的TTL似乎是正确的。这些地址可以从全球各地解决：http://whoer.net/checkwhois?host=teamcomp.net，https://pulse.turbobytes.com/results/56704afbecbe402ea700094c/，https://dnschecker.org/# A/teamcomp.net，https://www.whatsmydns.net/#A/teamcomp。net –