pc losing ability to resolve dns
davad
I have a problem with my laptop. After browsing the
internet for awhile (random amount of time). I notice
that my pc loses the ability to resolve urls. I can ping
ips all day, but if i put in a www. i get nothing. I
have loaded two different operating systems on this
machine and switched the NIC as well. The problem has
gotten better as of late (it can go for days without
losing resolution), but still persists. A reboot always
corrects the issue as well. I'm not running any special
firewall on the system either and my regular pc,
configured the same way, never has this problem.
The kicker is, the other day, I came across another
computer having the same problem, only much worse. After
a few pages, it too, loses the ability to surf.
Any ideas out there?
thanks,
dave..
Ace Fekay [MVP]
davad <da...@sbcglobal.net> posted his concerns then I replied down below:
What DNS addresses are you using? Can you provide an ipconfig /all of one of
the offending machine?
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
Dave
answer is several. I have pointed to various DNS servers
with the same result.
>.
>
Kevin D. Goodknecht Sr. [MVP]
Dave <da...@sbcglobal.net>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
> If you are asking what DNS servers I am using, the
> answer is several. I have pointed to various DNS servers
> with the same result.
>
monitor and you won't even throw us a bone are we just supposed to make a
wild guess?
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
--
Hope This Helps
++++++++++++++++++++++++++++++++++++++++++
When responding to posts, please "Reply to Group" or
"Reply All" via your newsreader so that others may learn
and benefit from your issue
==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================
Ace Fekay [MVP]
Dave <da...@sbcglobal.net> posted his concerns then I replied down below:
> If you are asking what DNS servers I am using, the
> answer is several. I have pointed to various DNS servers
> with the same result.
>
Tough to guess without some info Dave. Help us out.
Ace Fekay [MVP]
Dave <da...@sbcglobal.net> posted his concerns then I replied down below:
> If you are asking what DNS servers I am using, the
> answer is several. I have pointed to various DNS servers
> with the same result.
>
Besides the (unedited) ipconfig /all, can you let us know your config?
Using AD?
Connection type: ADSL? T1? Cable?
Router type?
Any errors in the Event logs? Post the Event ID #s please.
Dave
I have multiple computers on the network. Only one has
this problem. All computers point to the same DNS
server. For troubleshooting purposes, I have pointed the
laptop to other dns servers, but the problem persists.
Also, I have recently come across another pc on an
entirely different network that is having the same
problem. The problem is not with the DNS servers, as no
other pc on either network has this issue. What I was
wondering is what could cause this.
thanks,
dave..
>.
>
Ace Fekay [MVP]
>
> I have multiple computers on the network. Only one has
> this problem. All computers point to the same DNS
> server. For troubleshooting purposes, I have pointed the
> laptop to other dns servers, but the problem persists.
> Also, I have recently come across another pc on an
> entirely different network that is having the same
> problem. The problem is not with the DNS servers, as no
> other pc on either network has this issue. What I was
> wondering is what could cause this.
>
> thanks,
>
> dave..
Ok, guessing mode...
Any errors in the Event viewer?
Any services (needed, but unknowingly) disabled? There are a few that are
needed for resolution to work.
Is it a firewall/proxy client?
SMS?
What OS is it?
Kevin D. Goodknecht Sr. [MVP]
Ace Fekay [MVP] <PleaseSubstituteMyFirstName&LastNa...@hotmail.com>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
Hmm,
Must be something top secret about his DNS server?
I bet he is using his ISP's DNS but he wants to beat around the bush about
it.
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
then I replied down below:
> Hmm,
> Must be something top secret about his DNS server?
> I bet he is using his ISP's DNS but he wants to beat around the bush
> about it.
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
We'll never know unless he helps us to help him.
We're kind of like doctors....
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
Dave
servers...the problem is not with the DNS servers, the
problem is something on the machine. It is happening on
two different machines on two different networks. I was
wondering what could cause this.
In my original post I explained that the problem on the
laptop has held on to this problem through different OS
installs (with complete partition deletion and
recreation) and different network cards. I am thinking a
piece of hardware might be to blame, but since I changed
the card, I was hoping to get some ideas as to what to
look at. The other computers on the same network do not
have this problem, so the problem cannot have ANYTHING to
do with the dns servers.
I am not trying to be hard headed or secretive about
anything. I would just like someone to answer the
question.
regards,
dave..
>.
>
Kevin D. Goodknecht Sr. [MVP]
Dave <da...@sbcglobal.net>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
> servers...the problem is not with the DNS servers, the
> problem is something on the machine. It is happening on
> two different machines on two different networks. I was
> wondering what could cause this.
>
> In my original post I explained that the problem on the
> laptop has held on to this problem through different OS
> installs (with complete partition deletion and
> recreation) and different network cards. I am thinking a
> piece of hardware might be to blame, but since I changed
> the card, I was hoping to get some ideas as to what to
> look at. The other computers on the same network do not
> have this problem, so the problem cannot have ANYTHING to
> do with the dns servers.
>
> I am not trying to be hard headed or secretive about
> anything. I would just like someone to answer the
> question.
>
to see if they are answering. To get a verbose out put run
nslookup -d2
to change servers type
server <server ip address>
Try all dns servers you have listed in TCP/IP properties to make sure all
servers are operating and answering all requests. Since a reboot corrects
the problem I suspect a lame or not operational or mis-configured server.
You have to remember that Windows TCP/IP will only go through the list once
it will not start using a previous server in the list without a reboot.
If you have not done this, then you have not tried everything. If you are
convinced it is a hardware issue then you are posting in the wrong group.
I am not clarvioent and cannot see your monitor I will help you, but you
will not help me help you.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Ace Fekay [MVP]
Dave <da...@sbcglobal.net> posted his concerns then I replied down below:
Try that test that Kevin mentioned.
If you don't want to give us any config info about this specific machine
that is having the problem or tell us if there are any errors in it's Event
logs, then it's guessing time and there are too many factors to guess.
And as I posted earlier with those questions about what your setup/config
is, I would, if I were you, double check and make sure the config on this
machine is the same as the ones without the problems.
Dave, it's really tough to help if you can't give us any configuration
information. Guessing just doesn't do us or you any good. If we guess one
thing, you may turn around and say, NO, It;'s not that! We'll guess
someothing else, and you may come back with the same answer. So if have
something concrete to go on, it will help narrow it down.
So far from the information you provided, it's as if we're just looking at a
menu in a restaurant without knowing the ingredients and the way it was
prepared and you're calorie pinching. So in that case, YOU'LL ask the waiter
a few questions to determine if you want the dish or not.
In the same manner, we need to know what your settings and errors are and
your config so we can help out.
See if you an answer those questions I previously posted. For your
convenience, here they are again with a couple others added.
Any errors in the Event viewer?
Any services (needed, but unknowingly) disabled? There are a few that are
needed for resolution to work.
Is it a firewall/proxy client?
SMS?
What OS is it?
Do you have AD running?
What DNS server IP addresses are you using?
Thanks Dave. Otherwise, it will be difficult to help.
If you can't provide it because of the information's sensitivity, I would
suggest to call Microsoft PSS (Product Support Services). The engineers
there will help you out. Matter of fact they monitor these newsgroups and
usually jump in with suggestions and collaborate with the MVPs to help out
you, the public. If you feel that the information is too sensitive to post
in the public forums, I would suggest to call them.
For your convenience, here's the MS PSS page to contact Microsoft and their
phone numbers, depending on what OS version what product you're having
problems with, etc:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
Good luck.
Ace Fekay [MVP]
Dave <da...@sbcglobal.net> posted his concerns then I replied down below:
> As I originally said...I have used several different DNS
> servers...the problem is not with the DNS servers, the
> problem is something on the machine. It is happening on
> two different machines on two different networks. I was
> wondering what could cause this.
>
> In my original post I explained that the problem on the
> laptop has held on to this problem through different OS
> installs (with complete partition deletion and
> recreation) and different network cards. I am thinking a
> piece of hardware might be to blame, but since I changed
> the card, I was hoping to get some ideas as to what to
> look at. The other computers on the same network do not
> have this problem, so the problem cannot have ANYTHING to
> do with the dns servers.
>
> I am not trying to be hard headed or secretive about
> anything. I would just like someone to answer the
> question.
>
> regards,
>
> dave..
Love to answer the question. But there are numerous factors that will cause
this.
Dave, at this point you haven't even told us what operating system is on
your laptop. If you need to reinstall TCP/IP if you feel that will help,
there are different procdedures for each OS.
Crazy
Dave <da...@sbcglobal.net>
> As I originally said...I have used several different DNS
> servers...the problem is not with the DNS servers, the
> problem is something on the machine. It is happening on
> two different machines on two different networks. I was
> wondering what could cause this.
>
> In my original post I explained that the problem on the
> laptop has held on to this problem through different OS
> installs (with complete partition deletion and
> recreation) and different network cards. I am thinking a
> piece of hardware might be to blame, but since I changed
> the card, I was hoping to get some ideas as to what to
> look at. The other computers on the same network do not
> have this problem, so the problem cannot have ANYTHING to
> do with the dns servers.
>
> I am not trying to be hard headed or secretive about
> anything. I would just like someone to answer the
> question.
>
dave..
It sounds to me like you are. What was your question?
Or is this a test?
Yep, I'm convinced its the hardware thow it away and get a new one.
That is about the best answer you are going to get on the information you've
given these guys.
Why are you wasting their time with this?
Everything they've tried to recommend you've thown out so why don't you just
get a new one.
Crazy
Kevin D. Goodknecht Sr. [MVP]
Then Kevin D4Dad added his reply at the bottom.
Just to add, I see you have a sbcglobal.net email address do you have either
of these DNS servers in your TCP/IP?
151.164.1.1 and/or 151.164.1.7
These are SBC's Authoritative DNS server they will NOT answer
non-authoritatively, they will only answer authoritatively.
They have recursion disabled on them, so if you are using them remove them
from anywhere in the network they are being used, these two servers cannot
be used as forwarders either.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
then I replied down below:
> either of these DNS servers in your TCP/IP?
> 151.164.1.1 and/or 151.164.1.7
>
> These are SBC's Authoritative DNS server they will NOT answer
> non-authoritatively, they will only answer authoritatively.
> They have recursion disabled on them, so if you are using them remove
> them from anywhere in the network they are being used, these two
> servers cannot be used as forwarders either.
>
>
WHen I tried it, with the d2 option, it said they were allowing recursion,
unless I looked in the wrong spot.
Kevin D. Goodknecht Sr. [MVP]
Ace Fekay [MVP] <PleaseSubstituteMyFirstName&LastNa...@hotmail.com>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
>
> When I tried it, with the d2 option, it said they were allowing
> recursion, unless I looked in the wrong spot.
> --
> Regards,
> Ace
>
> Please direct all replies to the newsgroup so all can benefit.
>
> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
> Microsoft Windows MVP - Active Directory
This is the answer from SBC's recursive DNS at 151.164.1.8 notice the answer
for want recursion, recursion avail.
------------
Got answer (107 bytes):
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 5, authority records = 0, additional = 0
This is the answer you will get from SBC's non recursive 151.164.1.1 notice
the absence of an answer for want recursion
------------
Got answer (171 bytes):
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, want recursion
questions = 1, answers = 0, authority records = 4, additional = 4
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
then I replied down below:
I tried it the same way with my own server and got the same thing. But if
you look down at the next section, it shows that recursion is available:
=================================
Name: mail.bandwidthpros.com
Address: 208.47.39.10
> server 208.47.39.10
------------
SendRequest(), len 43
HEADER:
opcode = QUERY, id = 14, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
10.39.47.208.in-addr.arpa, type = PTR, class = IN
------------
truncated answer
------------
Got answer (531 bytes):
HEADER:
opcode = QUERY, id = 14, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 16, authority records = 0, additional =
0
====================================
If you tried it with your own server, what do you find?
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
Jonathan de Boyne Pollard
The methods of problem diagnosis are the same in many walks of life, from
doctors treating patients to car mechanics fixing vehicle breakdowns. It's
amazing how many people think that problems with computers are somehow exempt
from the requirements for complete and accurate information that are there in
all other walks of life, and as a consequence present their computer problems
on free technical support forums in a way that would earn them very short
shrift indeed were they to do similar with a doctor or a mechanic whose time
and assistance they weren't paying for.
I suspect that only an exceptionally masochistic doctor would indulge the
following kind of timewasting for free:
Patient: Doctor, if I move one of my limbs for a while,
I encounter problems. Any ideas ?
Doctor: What sort of problems ? Which limb are you
moving ? How are you moving it ?
Patient: I said already. It's one of my limbs.
Doctor: It's tough to guess which limb. Please tell me.
Patient: It happens with the limb on the other side, too.
Doctor: But what are you doing, what actually happens, and
which part of your body is involved ? I'm a
doctor. I need a description of your symptoms to
work with and you aren't telling me a single thing.
Patient: I'm not trying to be hard headed or secretive.
I just want you to answer my question.
Jonathan de Boyne Pollard
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/problem-report-standard-litany.html>
Tell us:
* The domain name portions of those URLs.
* The exact error messages presented by your web browser.
Then try manual "A" resource record lookups, with "dig" (or an
equivalent), on the same machine against those domain names;
and show us:
* The exact tests that you performed.
* The complete results of those tests.
Kevin D. Goodknecht Sr. [MVP]
> I tried it the same way with my own server and got the same thing.
The first one is the send request the second is the answer, if recursion is
disabled it will not answer will recursion available.
Look at this this is the query for one of my public domains against SBC's
ns1.swbell.net which has recursion disabled, notice in the answer section
the recursion avail statement is missing. Instead of answering with what
would be normal output from a type A query it answers with a referal to the
Authoritative NS
> lsaol.com.
Server: ns1.swbell.net
Address: 151.164.1.1
------------
SendRequest(), len 27
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
lsaol.com, type = A, class = IN
------------
------------
Got answer (171 bytes):
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, want recursion
questions = 1, answers = 0, authority records = 4, additional = 4
QUESTIONS:
lsaol.com, type = A, class = IN
AUTHORITY RECORDS:
-> lsaol.com
type = NS, class = IN, dlen = 8
nameserver = KJWEB.lsaol.com
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
-> lsaol.com
type = NS, class = IN, dlen = 6
nameserver = NS1.lsaol.com
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
-> lsaol.com
type = NS, class = IN, dlen = 12
nameserver = NS1.ZODNS.com
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
-> lsaol.com
type = NS, class = IN, dlen = 6
nameserver = NS2.lsaol.com
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
ADDITIONAL RECORDS:
-> KJWEB.lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.209
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
-> NS1.lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.209
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
-> NS1.ZODNS.com
type = A, class = IN, dlen = 4
internet address = 66.114.69.151
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
-> NS2.lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.212
ttl = 154516 (1 day 18 hours 55 mins 16 secs)
------------
Name: lsaol.com
Served by:
- KJWEB.lsaol.com
65.65.91.209
lsaol.com
- NS1.lsaol.com
65.65.91.209
lsaol.com
- NS1.ZODNS.com
66.114.69.151
lsaol.com
- NS2.lsaol.com
65.65.91.212
lsaol.com
But the same query ran against recursive 151.164.1.8 there is a much
different answer it returns the lookup of all the A records for lsaol.com.
Also notice in the Got Answer section the recursion avail. statement is
there.
> lsaol.com.
Server: dns1.rcsntx.sbcglobal.net
Address: 151.164.1.8
------------
SendRequest(), len 27
HEADER:
opcode = QUERY, id = 12, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
lsaol.com, type = A, class = IN
------------
------------
Got answer (107 bytes):
HEADER:
opcode = QUERY, id = 12, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 5, authority records = 0, additional = 0
QUESTIONS:
lsaol.com, type = A, class = IN
ANSWERS:
-> lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.213
ttl = 600 (10 mins)
-> lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.212
ttl = 600 (10 mins)
-> lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.210
ttl = 600 (10 mins)
-> lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.209
ttl = 600 (10 mins)
-> lsaol.com
type = A, class = IN, dlen = 4
internet address = 65.65.91.211
ttl = 600 (10 mins)
------------
Name: lsaol.com
Addresses: 65.65.91.213, 65.65.91.212, 65.65.91.210, 65.65.91.209
65.65.91.211
The same request against my primary server again notice the recursion avail
statement along with the Authority records.
> lsaol.com
Server: kjweb.lsaol.com
Address: 65.65.91.209
------------
SendRequest(), len 37
HEADER:
opcode = QUERY, id = 25, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
lsaol.com.lsaol.com, type = A, class = IN
------------
------------
Got answer (94 bytes):
HEADER:
opcode = QUERY, id = 25, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
lsaol.com.lsaol.com, type = A, class = IN
AUTHORITY RECORDS:
-> lsaol.com
type = SOA, class = IN, dlen = 36
ttl = 172800 (2 days)
primary name server = kjweb.lsaol.com
responsible mail addr = admin.lsaol.com
serial = 2003071205
refresh = 3600 (1 hour)
retry = 900 (15 mins)
expire = 604800 (7 days)
default TTL = 172800 (2 days)
------------
Here is the lookup I get on your domain against my server
> mail.bandwidthpros.com.
Server: kjweb.lsaol.com
Address: 65.65.91.209
------------
SendRequest(), len 40
HEADER:
opcode = QUERY, id = 31, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
mail.bandwidthpros.com, type = A, class = IN
------------
------------
Got answer (56 bytes):
HEADER:
opcode = QUERY, id = 31, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
mail.bandwidthpros.com, type = A, class = IN
ANSWERS:
-> mail.bandwidthpros.com
type = A, class = IN, dlen = 4
internet address = 208.47.39.10
ttl = 86388 (23 hours 59 mins 48 secs)
------------
Non-authoritative answer:
Name: mail.bandwidthpros.com
Address: 208.47.39.10
But when I run it against SBC's Authoritative non recursive it gets refered
to the GTLD servers.
> bandwidthpros.com.
Server: ns1.swbell.net
Address: 151.164.1.1
------------
SendRequest(), len 35
HEADER:
opcode = QUERY, id = 37, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
bandwidthpros.com, type = A, class = IN
------------
------------
Got answer (467 bytes):
HEADER:
opcode = QUERY, id = 37, rcode = NOERROR
header flags: response, want recursion
questions = 1, answers = 0, authority records = 13, additional =
13
QUESTIONS:
bandwidthpros.com, type = A, class = IN
AUTHORITY RECORDS:
-> com
type = NS, class = IN, dlen = 20
nameserver = A.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = G.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = H.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = C.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = I.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = B.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = D.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = L.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = F.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = J.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = K.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = E.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = M.GTLD-SERVERS.NET
ttl = 116391 (1 day 8 hours 19 mins 51 secs)
ADDITIONAL RECORDS:
-> A.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.5.6.30
ttl = 109517 (1 day 6 hours 25 mins 17 secs)
-> G.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.42.93.30
ttl = 158677 (1 day 20 hours 4 mins 37 secs)
-> H.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.54.112.30
ttl = 40724 (11 hours 18 mins 44 secs)
-> C.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.26.92.30
ttl = 46580 (12 hours 56 mins 20 secs)
-> I.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.43.172.30
ttl = 118336 (1 day 8 hours 52 mins 16 secs)
-> B.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.33.14.30
ttl = 128851 (1 day 11 hours 47 mins 31 secs)
-> D.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.31.80.30
ttl = 48647 (13 hours 30 mins 47 secs)
-> L.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.41.162.30
ttl = 52104 (14 hours 28 mins 24 secs)
-> F.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.35.51.30
ttl = 51603 (14 hours 20 mins 3 secs)
-> J.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.48.79.30
ttl = 164066 (1 day 21 hours 34 mins 26 secs)
-> K.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.52.178.30
ttl = 3516 (58 mins 36 secs)
-> E.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.12.94.30
ttl = 45393 (12 hours 36 mins 33 secs)
-> M.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.55.83.30
ttl = 55430 (15 hours 23 mins 50 secs)
------------
Name: bandwidthpros.com
Served by:
- A.GTLD-SERVERS.NET
192.5.6.30
com
- G.GTLD-SERVERS.NET
192.42.93.30
com
- H.GTLD-SERVERS.NET
192.54.112.30
com
- C.GTLD-SERVERS.NET
192.26.92.30
com
- I.GTLD-SERVERS.NET
192.43.172.30
com
- B.GTLD-SERVERS.NET
192.33.14.30
com
- D.GTLD-SERVERS.NET
192.31.80.30
com
- L.GTLD-SERVERS.NET
192.41.162.30
com
- F.GTLD-SERVERS.NET
192.35.51.30
com
- J.GTLD-SERVERS.NET
192.48.79.30
com
Kevin D. Goodknecht Sr. [MVP]
Jonathan de Boyne Pollard <J.deBoyn...@tesco.net>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
I suppose the doctor should tell him what Crazy said in his post, since it
is causing you problems, let's just amputate the one that I guess it is and
hope, I amputate the right one.
ROFLOL
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Ace Fekay [MVP]
>
Ahh, I'm just a cook...
:-)
Ace
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
then I replied down below:
Ok, I see what you mean. I didn't look down further for the referral. The
top portion when I ran it says it's available. Look:
C:\>nslookup
Default Server: ponyexpress.bandwidthpros.com
Address: 208.47.39.10
> set d2
> server 151.164.1.1
------------
SendRequest(), len 42
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
1.1.164.151.in-addr.arpa, type = PTR, class = IN
------------
------------
Got answer (134 bytes):
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 1, authority records = 2, additional = 2
QUESTIONS:
1.1.164.151.in-addr.arpa, type = PTR, class = IN
ANSWERS:
-> 1.1.164.151.in-addr.arpa
type = PTR, class = IN, dlen = 16
name = ns1.swbell.net
ttl = 7200 (2 hours)
AUTHORITY RECORDS:
-> 1.164.151.in-addr.arpa
type = NS, class = IN, dlen = 2
nameserver = ns1.swbell.net
ttl = 172800 (2 days)
-> 1.164.151.in-addr.arpa
type = NS, class = IN, dlen = 6
nameserver = ns2.swbell.net
ttl = 172800 (2 days)
ADDITIONAL RECORDS:
-> ns1.swbell.net
type = A, class = IN, dlen = 4
internet address = 151.164.1.1
ttl = 900 (15 mins)
-> ns2.swbell.net
type = A, class = IN, dlen = 4
internet address = 151.164.1.7
ttl = 900 (15 mins)
------------
Default Server: ns1.swbell.net
Address: 151.164.1.1
> bandwidthpros.com
Server: ns1.swbell.net
Address: 151.164.1.1
------------
SendRequest(), len 53
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
bandwidthpros.com.bandwidthpros.com, type = A, class = IN
------------
------------
Got answer (485 bytes):
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, want recursion
questions = 1, answers = 0, authority records = 13, additional =
13
QUESTIONS:
bandwidthpros.com.bandwidthpros.com, type = A, class = IN
AUTHORITY RECORDS:
-> com
type = NS, class = IN, dlen = 20
nameserver = A.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = G.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = H.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = C.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = I.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = B.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = D.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = L.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = F.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = J.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = K.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = E.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = M.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
ADDITIONAL RECORDS:
-> A.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.5.6.30
ttl = 35986 (9 hours 59 mins 46 secs)
-> G.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.42.93.30
ttl = 85146 (23 hours 39 mins 6 secs)
-> H.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.54.112.30
ttl = 139994 (1 day 14 hours 53 mins 14 secs)
-> C.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.26.92.30
ttl = 145850 (1 day 16 hours 30 mins 50 secs)
-> I.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.43.172.30
ttl = 44805 (12 hours 26 mins 45 secs)
-> B.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.33.14.30
ttl = 55320 (15 hours 22 mins)
-> D.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.31.80.30
ttl = 147917 (1 day 17 hours 5 mins 17 secs)
-> L.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.41.162.30
ttl = 151374 (1 day 18 hours 2 mins 54 secs)
-> F.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.35.51.30
ttl = 150873 (1 day 17 hours 54 mins 33 secs)
-> J.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.48.79.30
ttl = 90535 (1 day 1 hour 8 mins 55 secs)
-> K.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.52.178.30
ttl = 102786 (1 day 4 hours 33 mins 6 secs)
-> E.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.12.94.30
ttl = 144663 (1 day 16 hours 11 mins 3 secs)
-> M.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.55.83.30
ttl = 154700 (1 day 18 hours 58 mins 20 secs)
------------
------------
SendRequest(), len 35
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
bandwidthpros.com, type = A, class = IN
------------
------------
Got answer (467 bytes):
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: response, want recursion
questions = 1, answers = 0, authority records = 13, additional =
13
QUESTIONS:
bandwidthpros.com, type = A, class = IN
AUTHORITY RECORDS:
-> com
type = NS, class = IN, dlen = 20
nameserver = A.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = G.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = H.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = C.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = I.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = B.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = D.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = L.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = F.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = J.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = K.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = E.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
-> com
type = NS, class = IN, dlen = 4
nameserver = M.GTLD-SERVERS.NET
ttl = 34117 (9 hours 28 mins 37 secs)
ADDITIONAL RECORDS:
-> A.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.5.6.30
ttl = 35986 (9 hours 59 mins 46 secs)
-> G.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.42.93.30
ttl = 85146 (23 hours 39 mins 6 secs)
-> H.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.54.112.30
ttl = 139994 (1 day 14 hours 53 mins 14 secs)
-> C.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.26.92.30
ttl = 145850 (1 day 16 hours 30 mins 50 secs)
-> I.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.43.172.30
ttl = 44805 (12 hours 26 mins 45 secs)
-> B.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.33.14.30
ttl = 55320 (15 hours 22 mins)
-> D.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.31.80.30
ttl = 147917 (1 day 17 hours 5 mins 17 secs)
-> L.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.41.162.30
ttl = 151374 (1 day 18 hours 2 mins 54 secs)
-> F.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.35.51.30
ttl = 150873 (1 day 17 hours 54 mins 33 secs)
-> J.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.48.79.30
ttl = 90535 (1 day 1 hour 8 mins 55 secs)
-> K.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.52.178.30
ttl = 102786 (1 day 4 hours 33 mins 6 secs)
-> E.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.12.94.30
ttl = 144663 (1 day 16 hours 11 mins 3 secs)
-> M.GTLD-SERVERS.NET
type = A, class = IN, dlen = 4
internet address = 192.55.83.30
ttl = 154700 (1 day 18 hours 58 mins 20 secs)
>
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
Ace Fekay [MVP]
Jonathan de Boyne Pollard <J.deBoyn...@tesco.net> posted his concerns
then I replied down below:
Sounds almost like the Monty Python skit in the "Search for the Holly
Grail"...
Kevin D. Goodknecht Sr. [MVP]
> In news:OBygdWcS...@TK2MSFTNGP10.phx.gbl,
> Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his
> concerns then I replied down below:
>
> Ok, I see what you mean. I didn't look down further for the referral.
> The top portion when I ran it says it's available. Look:
>
When you type server 151.164.1.1 since you are pointing to your DNS it is
running a reverse lookup on the the IP address you entered. I guess this is
one of those confusing things nslookup does that Jonathan is always ranting
about.
Anyway the top section, where you entered change server command is your name
server answer for the lookup you ran against it doing the reverse lookup on
SBC's IP address. If you take a closer look your DNS return the authority
records on the IP address.
--
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
then I replied down below:
But if you notice, I changed servers. Look back at the output. I was
actually using 151.164.1.7 and not my own server.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
Ace Fekay [MVP]
Ace Fekay [MVP] <PleaseSubstituteMyFirstName&LastNa...@hotmail.com>
posted his concerns then I replied down below:
Kevin, check this out:
C:\bind>dig @151.164.1.7 lsaol.net any
; <<>> DiG 9.2.2rc1 <<>> @151.164.1.7 lsaol.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;lsaol.net. IN ANY
;; ANSWER SECTION:
lsaol.net. 172800 IN NS ns1.lsaol.com.
lsaol.net. 172800 IN NS ns2.lsaol.com.
;; AUTHORITY SECTION:
lsaol.net. 172800 IN NS ns1.lsaol.com.
lsaol.net. 172800 IN NS ns2.lsaol.com.
;; ADDITIONAL SECTION:
ns1.lsaol.com. 172800 IN A 65.65.91.209
ns2.lsaol.com. 172800 IN A 65.65.91.212
;; Query time: 125 msec
;; SERVER: 151.164.1.7#53(151.164.1.7)
;; WHEN: Mon Jul 14 23:55:02 2003
;; MSG SIZE rcvd: 132
And This:==================================
C:\bind>dig @151.164.1.7 www.lsaol.net any
; <<>> DiG 9.2.2rc1 <<>> @151.164.1.7 www.lsaol.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.lsaol.net. IN ANY
;; ANSWER SECTION:
www.lsaol.net. 3600 IN A 65.65.91.209
;; Query time: 140 msec
;; SERVER: 151.164.1.7#53(151.164.1.7)
;; WHEN: Mon Jul 14 23:55:39 2003
;; MSG SIZE rcvd: 47
C:\bind>
Jonathan de Boyne Pollard
AF> allowing recursion, unless I looked in the wrong spot.
Kevin said that 151.164.1.1 and 151.164.1.7 are the "sbcglobal.net."
content DNS servers. However, the listings in the public DNS
database that are visible from here give 206.13.28.11 instead of
151.164.1.7 :
[C:\]dnsgetns sbcglobal.net.
206.13.28.11
151.164.1.1
[C:\]
Responses from both of those content DNS servers to here have
the RA flag set to 0:
[C:\]dnsqry /serverip:151.164.1.1 soa sbcglobal.net. | grep /b/u "(Header:|->)"
[0.0.0.0:0000] -> [151.164.1.1:0035] 31
Header: 0000 1+0+0+0, Q, , query, no_error
[151.164.1.1:0035] -> [0.0.0.0:0000] 157
Header: 0000 1+1+2+2, R, AUTH, query, no_error
[C:\]dnsqry /serverip:206.13.28.11 soa sbcglobal.net. | grep /b/u "(Header:|->)"
[0.0.0.0:0000] -> [206.13.28.11:0035] 31
Header: 0000 1+0+0+0, Q, , query, no_error
[206.13.28.11:0035] -> [0.0.0.0:0000] 157
Header: 0000 1+1+2+2, R, AUTH, query, no_error
[C:\]
Responses from 151.164.1.7 to here, however, have the
RA flag set to 1:
[C:\]dnsqry /serverip:151.164.1.7 soa sbcglobal.net. | grep /b/u "(Header:|->)"
[0.0.0.0:0000] -> [151.164.1.7:0035] 31
Header: 0000 1+0+0+0, Q, , query, no_error
[151.164.1.7:0035] -> [0.0.0.0:0000] 157
Header: 0000 1+1+2+2, R, RA|AUTH, query, no_error
[C:\]
Kevin D. Goodknecht Sr. [MVP]
Ace Fekay [MVP] <PleaseSubstituteMyFirstName&LastNa...@hotmail.com>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
> In news:u0VRfbnS...@tk2msftngp13.phx.gbl,
> Ace Fekay [MVP] <PleaseSubstituteMyFirstName&LastNa...@hotmail.com>
> posted his concerns then I replied down below:
>
> Kevin, check this out:
>
> C:\bind>dig @151.164.1.7 lsaol.net any
>
> ; <<>> DiG 9.2.2rc1 <<>> @151.164.1.7 lsaol.net any
recursive and ns2.swbell allows recursion ns2 holds secondary zones for ns1
and after talking to them about hosting a secondary zone for
lonestaramerica.com I found something interesting the any zone on ns1 is
replicated to the ns2 name server.
I'm not exactly sure how they do that but it is interesting that it happens
I guess I should have asked Patrick (one of the DNS admins) how this is
done.
Oh BTW, lsaol.net is about to go to AOL so it soon won't be mine, remember
me telling you of the agreement I made with them to settle the dispute over
lsaol.com and lsaol.net? They get one I get one.
Kevin D. Goodknecht Sr. [MVP]
Then Kevin D4Dad added his reply at the bottom.
Yes, Jonathan you are correct about that. But I was refering to SWBells DNS,
if you notice a couple of things about the SBCGlobal's NS record,
ns1.pbi.net (206.13.28.11) it belongs to Pacific Bell, which SW Bell aquired
sometime back to form SBC, not only does it not answer recursively, it also
does not have a delegation to the root. This means that not only does it not
answer non-authoritatively it won't refer you to the root for zones it
doesn't hold. So you certainly want to use it for anything accept as a place
to host a DNS domain zone.
My guess is that ns1.pbi.net is in California and I know for a fact that,
ns1 and ns2.swbell.net are in Texas
When I switched to SBC last year for my service I move my domains to their
DNS servers. I was requested to have ns1.swbell.net and ns2.swbell.net
listed as authoritative for the domains I moved. This was before I set up
DNS at my site because my old provider only gave me one IP address and they
charged me $6 a month for it. SBC gave me 5 IPs for $35 a month less than I
was paying. So it became a no brainer, I switched.
I know this sounds confusing :-) but the point I'm making is if he is trying
to use their Authoritative DNS servers anywhere in his setup as either
forwarders or in his NIC setup, it is going to cause inconsistant DNS
resolution problems. We've seen this before, when people have tried to use
some ISP's Authoritative DNS servers, that they get behavior Dave is
experiencing. But we will never know that I guess, because Dave won't tell
us what he is using for DNS.
Ace Fekay [MVP]
Jonathan de Boyne Pollard <J.deBoyn...@tesco.net> posted his concerns
then I replied down below:
>
> Kevin said that 151.164.1.1 and 151.164.1.7 are the "sbcglobal.net."
> content DNS servers. However, the listings in the public DNS
> database that are visible from here give 206.13.28.11 instead of
> 151.164.1.7 :
>
> [C:\]dnsgetns sbcglobal.net.
> 206.13.28.11
> 151.164.1.1
>
> [C:\]
>
> Responses from both of those content DNS servers to here have
> the RA flag set to 0:
So they are not offering recursive services.
>
> [C:\]dnsqry /serverip:151.164.1.1 soa sbcglobal.net. | grep /b/u
> "(Header:|->)" [0.0.0.0:0000] -> [151.164.1.1:0035] 31
> Header: 0000 1+0+0+0, Q, , query, no_error
> [151.164.1.1:0035] -> [0.0.0.0:0000] 157
> Header: 0000 1+1+2+2, R, AUTH, query, no_error
>
> [C:\]dnsqry /serverip:206.13.28.11 soa sbcglobal.net. | grep /b/u
> "(Header:|->)" [0.0.0.0:0000] -> [206.13.28.11:0035] 31
> Header: 0000 1+0+0+0, Q, , query, no_error
> [206.13.28.11:0035] -> [0.0.0.0:0000] 157
> Header: 0000 1+1+2+2, R, AUTH, query, no_error
>
> [C:\]
>
> Responses from 151.164.1.7 to here, however, have the
> RA flag set to 1:
So this one is. Interesting why they have it set up this way.
>
> [C:\]dnsqry /serverip:151.164.1.7 soa sbcglobal.net. | grep /b/u
> "(Header:|->)" [0.0.0.0:0000] -> [151.164.1.7:0035] 31
> Header: 0000 1+0+0+0, Q, , query, no_error
> [151.164.1.7:0035] -> [0.0.0.0:0000] 157
> Header: 0000 1+1+2+2, R, RA|AUTH, query, no_error
>
> [C:\]
Thanks Jonathan. I also did a Dig on the one above, and it gave me the same
info as far as the RA bit set: (I used Kevin's domain name here):
======================================
C:\bind>dig @151.164.1.7 lsaol.net any
; <<>> DiG 9.2.2rc1 <<>> @151.164.1.7 lsaol.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;lsaol.net. IN ANY
;; ANSWER SECTION:
lsaol.net. 172800 IN NS ns1.lsaol.com.
lsaol.net. 172800 IN NS ns2.lsaol.com.
;; AUTHORITY SECTION:
lsaol.net. 172800 IN NS ns1.lsaol.com.
lsaol.net. 172800 IN NS ns2.lsaol.com.
;; ADDITIONAL SECTION:
ns1.lsaol.com. 172800 IN A 65.65.91.209
ns2.lsaol.com. 172800 IN A 65.65.91.212
;; Query time: 125 msec
;; SERVER: 151.164.1.7#53(151.164.1.7)
;; WHEN: Mon Jul 14 23:55:02 2003
;; MSG SIZE rcvd: 132
===================================
But this one doesn't have the RA bit set. Just got the referral to the
GTLDs:
======================================
C:\bind>dig @151.164.1.1 www.lsaol.net any
; <<>> DiG 9.2.2rc1 <<>> @151.164.1.1 www.lsaol.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13
;; QUESTION SECTION:
;www.lsaol.net. IN ANY
;; AUTHORITY SECTION:
net. 116143 IN NS A.GTLD-SERVERS.net.
net. 116143 IN NS G.GTLD-SERVERS.net.
net. 116143 IN NS H.GTLD-SERVERS.net.
net. 116143 IN NS C.GTLD-SERVERS.net.
net. 116143 IN NS I.GTLD-SERVERS.net.
net. 116143 IN NS B.GTLD-SERVERS.net.
net. 116143 IN NS D.GTLD-SERVERS.net.
net. 116143 IN NS L.GTLD-SERVERS.net.
net. 116143 IN NS F.GTLD-SERVERS.net.
net. 116143 IN NS J.GTLD-SERVERS.net.
net. 116143 IN NS K.GTLD-SERVERS.net.
net. 116143 IN NS E.GTLD-SERVERS.net.
net. 116143 IN NS M.GTLD-SERVERS.net.
;; ADDITIONAL SECTION:
A.GTLD-SERVERS.net. 125458 IN A 192.5.6.30
G.GTLD-SERVERS.net. 1817 IN A 192.42.93.30
H.GTLD-SERVERS.net. 56665 IN A 192.54.112.30
C.GTLD-SERVERS.net. 62521 IN A 192.26.92.30
I.GTLD-SERVERS.net. 134277 IN A 192.43.172.30
B.GTLD-SERVERS.net. 144792 IN A 192.33.14.30
D.GTLD-SERVERS.net. 64588 IN A 192.31.80.30
L.GTLD-SERVERS.net. 68045 IN A 192.41.162.30
F.GTLD-SERVERS.net. 67544 IN A 192.35.51.30
J.GTLD-SERVERS.net. 7206 IN A 192.48.79.30
K.GTLD-SERVERS.net. 19457 IN A 192.52.178.30
E.GTLD-SERVERS.net. 61334 IN A 192.12.94.30
M.GTLD-SERVERS.net. 71371 IN A 192.55.83.30
;; Query time: 125 msec
;; SERVER: 151.164.1.1#53(151.164.1.1)
;; WHEN: Tue Jul 15 20:32:45 2003
;; MSG SIZE rcvd: 460
============================================
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
No problem. I haven't forgotten. Actually wanted to test it with your domain
to see what it was doing!
I see the RA on the one server set, as Jonathan pointed out, and did a Dig
on it to see myself. I have to fudge around with the syntax, since I don;'t
use it that often and even emailed William to point that out for me.
So the one server is offering recursion, but not the other, but, as William
mentioned to me, it's hard to tell if that server is actually forwarding on
or iteration. I guess the only way to tell is to plug it in, don't use the
Roots and see what happens.
Cheers!
Jonathan de Boyne Pollard
KDGS> that Jonathan is always ranting about.
Ranting ? Pah! I just explain that the daft error message that it produces
is the result of its bad design, describe what is actually happening, and
strongly encourage the use of one of the several widely available replacement
tools that do not have "nslookup"'s problem. That's not ranting. Ranting
involves violence, anger, or strong emotion, none of which are present in my
frequently given answer.
Moreover, it's far from just me alone that mentions this bad design, and that
encourages people to get out of the bad habit of using "nslookup". The same
thing has been said and the same encouragement made by _many_ people (for
quite a few years now), including Barry Margolin,
BM> The nslookup command sucks. Its error messages are
BM> either confusing or ambiguous [...] and it performs a
BM> reverse DNS check of the server's address that is not
BM> required by the protocol and causes lots of confusion.
BM> [...] consider using the "dig" or "host" programs
BM> instead, [...]
Paul Vixie,
PV> Nslookup is a bad command, for many reasons, and you
PV> should use "dig" for all command line DNS lookups
PV> unless you prefer "host" which is less general but
PV> more friendly.
Dan Bernstein,
DJB> Every server could add a PTR record to work around
DJB> this nslookup bug, but that creates unnecessary
DJB> administrative problems. It's easier to tell people
DJB> to stop using buggy [...] software.
and Kevin Darcy,
KD> This error is the result of nslookup's suckiness.
KD> [...] Use a real tool like dig [...]
just for starters. These and many other people all saying the same thing, in
just about every DNS discussion forum that there is, are what the Frequently
Given Answer is referring to when it briefly says
It has been widely acknowledged for several years that
["nslookup"] is a bad tool.
Jonathan de Boyne Pollard
Not to me, it doesn't. But then I tell people not to do that too. (-:
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-server-roles.html#ContentDontTalkToClients>
What I didn't see was where you got the 151.164.1.7 address from,
since that's not one of the listed "sbcglobal.net." content DNS
servers. It's clear now, however, that it came from your own
dealings with SBC. (-:
Jonathan de Boyne Pollard
KDGS> also does not have a delegation to the root. This means that
KDGS> not only does it not answer non-authoritatively it won't refer
KDGS> you to the root for zones it doesn't hold.
This is not a cause of a problem, however. Because of the way that
securing against cache pollution works, upwards referrals such as
that have to be entirely discarded by a secure resolving proxy
DNS server anyway.
There's a belief held by a few, including the foolish "fr." registry,
that every content DNS server should provide one with delegation
information for "." if it is asked. (The foolish "fr." registry has
daft automated checks that it runs against all of the content DNS
servers for "fr." domains that needlessly query them for this
information amongst other things.) But this belief is false. A
DNS server that is only serving content has no need to publish
anything about "." if it is _not_ actually a "." content DNS
server in its own right.
Indeed, publishing such delegation information would trigger one
of the several bugs in the broken "dnstracer" utility. So
accommodating the brokenness of "dnstracer" is one (admittedly
poor) reason not to do so.
Kevin D. Goodknecht Sr. [MVP]
Here's the deal Jonathan, swbell.net is in Texas, Oklahoma, Arkansas, and
Missiouri their name servers are geographically located for these states
> swbell.net
Server: ns1.lonestaramerica.com
Address: 65.65.91.209
Non-authoritative answer:
swbell.net nameserver = ns1.swbell.net
swbell.net nameserver = ns2.swbell.net
ns1.swbell.net internet address = 151.164.1.1<non-recursive
ns2.swbell.net internet address = 151.164.1.7
Pacific Bell (pbi.net) is California and West coast their name servers are
geographcally located on the West coast
> pbi.net
Server: ns1.lonestaramerica.com
Address: 65.65.91.209
Non-authoritative answer:
pbi.net nameserver = ns2.pbi.net
pbi.net nameserver = ns1.pbi.net
ns2.pbi.net internet address = 206.13.29.11
ns1.pbi.net internet address = 206.13.28.11<non-recursive
SBC is the Corp formed from the two Baby Bells above so it would seem likely
that they will have sbcglobal.net name servers for each geographcal location
But these two name servers will not recurse the internet name space they
have recursion disabled. Is it not believable that some one might try to use
one of these two name servers for DNS?
> sbcglobal.net
Server: ns1.lonestaramerica.com
Address: 65.65.91.209
Non-authoritative answer:
sbcglobal.net nameserver = ns1.swbell.net
sbcglobal.net nameserver = ns1.pbi.net
ns1.swbell.net internet address = 151.164.1.1<non-recursive
ns1.pbi.net internet address = 206.13.28.11<non-recursive
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.LSAOL.COM> posted his concerns
then I replied down below:
<snip>
What a mess with the break up of the "Bells"!
Kevin D. Goodknecht Sr. [MVP]
> KDGS> I guess this is one of those confusing things nslookup does
> KDGS> that Jonathan is always ranting about.
>
> Ranting ? Pah! I just explain that the daft error message that it
> produces is the result of its bad design, describe what is actually
> happening, and strongly encourage the use of one of the several
> widely available replacement tools that do not have "nslookup"'s
> problem. That's not ranting. Ranting involves violence, anger, or
> strong emotion, none of which are present in my frequently given
> answer.
>
and on about nslookup being a bad tool I think that is extravegant speaking.
Then, you paste a link to a page where you go on and on about it being a bad
tool for having this behavior, when all they are asking for is why they get
domain not found when it starts. You seem to put a lot of emphesis on the
original poster's question and intent. Why not just tell them what the error
means and why they are getting it and let it go at that?
You won't even give a hint as to what to do to stop it.
So what if nslookup does a reverse lookup on the IP of the server it is
looking at. I don't think that makes it a bad tool, that is what nslookup is
supposed to do. So maybe dig doesn't do that, that doesn't make it superior.
Maybe dig is superior, but is it superior just because dig doesn't perform
that reverse lookup?
Whether nslookup performs the reverse lookup or not, I think has no bearing
on its performance.
Nslookup gives pretty much the same answer and in my humble oppinion it is
much easier to use, especially if you are doing multiple lookups. With my
hunt and peck style I would be all day making multiple lookups with dig.
Unless I am using the wrong command why should I have to type dig
@192.168.0.3 then the domain name just to do simple queries?
I just don't think that nslookup's behavior for looking up the name of the
server's IP it is looking has anything to do with it being inferior to dig.
It still gets the job done I have both dig and nslookup I use nslookup just
for its simplicity.