<- nslookup / dig -->
DougB at DougBarton.net
Sun Dec 15 22:33:48 UTC 2002
On Sun, 15 Dec 2002, almorton wrote:
> First i hope i'm not in the wrong newsgroup ....
This is the one.
> As far as i know, nslookup is deprecated & dig should be used instead
Correct, when it comes to dns debugging. For simple lookups, 'host' is
> yet, here the problem :
> news.wanadoo.fr = 18.104.22.168
Why do you say that? From where I sit (outside your network obviously):
news.wanadoo.fr has address 22.214.171.124
There are no problems with the delegation for wanadoo.fr, and
news.wanadoo.fr is not delegated. So, I'd say that the four authoritative
name servers for wanadoo.fr disagree with your assertion. :)
> if i do :
> nslookup news.wanadoo.fr 126.96.36.199
> => news.wanadoo.fr = 188.8.131.52
> right IP
Why are you querying 184.108.40.206? Is that a local resolver of some sort?
I can't reach it from here.
> They also have ns2.wanadoo.fr (220.127.116.11) and
> ns5.wanadoo.fr (18.104.22.168) but it *isn't* in the NIC and not SOA but
> will give the correct address
> for news.wanadoo.fr (ie 22.214.171.124)
I don't understand that part, sorry. That domain is delegated to:
nserver: ns.wanadoo.fr 126.96.36.199
nserver: ns2.wanadoo.fr 188.8.131.52
The .fr TLD name servers agree with whois.
I'm not sure that I really answered your question, but hopefully this will
"We have known freedom's price. We have shown freedom's power.
And in this great conflict, ... we will see freedom's victory."
- George W. Bush, President of the United States
State of the Union, January 28, 2002
Do YOU Yahoo!?
More information about the bind-users