问题原文
原帖链接 · Caius Jard · CC BY-SA 3.0
Currently I have a domain and rent a dedicated server for it. It runs a windows port of BIND (installed by/maintained by Plesk) and provides DNS relevant to my domain
I'm looking to wind down that dedicated server and have purchased another one (from OVH, as it happens) onto which a lot of my services have moved, but I haven't installed any DNS daemon on the new server. Instead I've created a zone for my domain on OVH's DNS servers via their control panel
Their support tell me that the last step I need to execute to switch everything over is to nominate their DNS servers as responsible for my domain, on the config pages of the registrar
The reason I haven't done so so far is that I cannot get their DNS servers to answer any queries! If I do this on my OVH server (note: ns108 is the DNS server that they have allocated to my account):
c:\> nslookup
> server ns108.ovh.net
Default Server: ns108.ovh.net
Addresses: 2001:41d0:1:1998::1
213.251.128.152
> google.com
*** ns108.ovh.net can't find google.com: No response from server
> server 213.251.128.152
Default Server: [213.251.128.152]
Address: 213.251.128.152
> google.com
*** [213.251.128.152] can't find google.com: Query refused
As noted their techs say "just switch it over, it'll all work fine", but it doesn't seem like much of a reassurance. If doesn't matter what domain I put into the query; the response is the same.
Is there a technical reason why their servers won't start responding until I nominate them as responsible for my domain, with the registrar? i.e. is what the techs telling me true, that I can switch and not worry? I don't really want to bring down every site we operate as a result of no-one being able to look up our main domain any more - that would be bad for business..
edit: Update:
I really struggled with inconsistent behaviour of nslookup here - the solutions below advised me to specify the OVH DNS server on the command line - I thought I HAD specified it (in the way I was using nslookup, by issuing a server dns108.ovh.net command after running nslookup) but it never worked out. I've since determined that it does work when specified in interactive mode, if I use the IPv4 IP of the server rather than its name. I can only assume it's because specifying by name in interactive mode causes the lookup of the server to return an IPv6 address (first) and I suspect this is the one being used, as my system isn't configured for IPv6
Working:
c:\> nslookup mail.mydomain.com dns108.ovh.net
c:\> nslookup mail.mydomain.com 213.251.188.152
c:\> nslookup
>server 213.251.188.152
>mail.mydomain.com
Not working:
c:\> nslookup
>server dns108.ovh.net
Default Server: dns108.ovh.net
Addresses: 2001:41d0:1:4a98::1
213.251.188.152
>mail.mydomain.com
c:\>ping 2001:41d0:1:1998::1
Pinging 2001:41d0:1:1998::1 with 32 bytes of data:
PING: transmit failed. General failure.
Thanks to all who helped me get to the bottom of this.. Apologies for the misdirection earlier, putting google.com into the example commands - i was using my actual domain, but also trying google and other common names for comparison. My understanding of DNS is now much improved!
已采纳解答
原帖链接 · Esa Jokinen · CC BY-SA 3.0
You simply don't (yet) understand the difference between authoritative and recursive DNS servers. Therefore, your testing is based on wrong assumptions. Corrected testing at the end of my answer.
In your OVH server, you use cdns.ovh.net as your recursive DNS server. It resolves ANY domain for you, when querying from your OVH server. That's usually preconfigured during installation, so you don't need to change anything. Also, cdns.ovh.net has nothing to do with your domain.
Instead, see OVH's New DNS servers guide:
Attention! : Since February 2007, OVH has implemented a series of new shared DNS servers. To check on which one your DNS domain is hosted, you must go to the OVH Manager, click on the field "Domain & DNS", "DNS Zone" option, and watch the 2 fields of the type NS (like
dnsXX.ovh.netandnsXX.ovh.net); so, for a newly created domain, here are the recommended configurations.
The site lists nameservers for different type of services (shared hosting, webhosting, dedicated server), but despite you have a dedicated server, you seem to have chosen to use their DNS servers instead, so what's said on that page doesn't directly apply to you.
You should go with what the OVH Manager and OVH support says. However, based on the pattern on that page I could guess that this server has a pair, and you should always specify at least two nameservers at the registar:
- Primary DNS:
dns108.ovh.netIP :213.251.188.152 - Secondary DNS:
ns108.ovh.netIP :213.251.128.152
First test that both these name servers answers authoritatively for your domain. You can do this from your own local computer, as this has nothing to do with your OVH server and serves the whole world, anyway. Here, the example.com represents your domain:
nslookup example.com dns108.ovh.net
nslookup example.com ns108.ovh.net
The servers are ready to be nominated if both tests passes both these conditions:
- Both servers answers for your domain and gives expected IP address.
The answers are authoritative i.e. in
nslookupthere's no lineNon-authoritative answer. Here, theb.iana-servers.netis authoritative forexample.combut thecdns.ovh.netisn't:$ nslookup example.com b.iana-servers.net Server: b.iana-servers.net Address: 2001:500:8d::53#53 Name: example.com Address: 93.184.216.34 $ nslookup example.com cdns.ovh.net Server: cdns.ovh.net Address: 2001:41d0:3:163::1#53 Non-authoritative answer: Name: example.com Address: 93.184.216.34
Hint: if OVH says the DNS for your domain is working, there's no reason to believe the tests wouldn't pass. They know what they are doing. But this is what you can do if you are still really suspicious.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
