PDA

View Full Version : No DNS cache at ISP?


Mandi
12-31-2000, 02:08 PM
I'll ask about the no www access. (I can view it that way.)

Domain has been registered and functional for over a month, and she previously had access, it quit working rather abruptly for her.

Domain is http://www.kerrysherbals.com/

I recall having trouble myself about a year ago, accessing one of my FQ sites via FTP and browser.[nbsp][nbsp]Everything was fine on the FQ end of course.[nbsp][nbsp]Ultimately, switching ISP's was the answer, so it must have been a DNS issue at the ISP.

I am a tiny bit suspicious that her webhost moved the server, thus changing the IP, and didn't tell anyone . . . and is using some sort of duplicate temporary system, which her ISP isn't caught up with.[nbsp][nbsp](Like the tunneling FQ did when they moved our servers to their present fancy digs awhile back . . . Labor Day?[nbsp][nbsp]I can't remember.)
[This message has been edited by Mandi (edited 01-01-01@3:22 pm)]

sheila
12-31-2000, 04:02 PM
Here is a traceroute from my machine to Kerry's Herbals (I was able to access her page):


12/31/00 11:36:47 Fast traceroute kerrysherbals.com
Trace kerrysherbals.com (64.177.53.155) ...
[nbsp]1 4.3.200.1[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]40ms[nbsp][nbsp] 41ms[nbsp][nbsp] 37ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](lsanca1-200-001.dsl.gtei.net ok)
[nbsp]2 4.24.62.37[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp] 29ms[nbsp][nbsp] 31ms[nbsp][nbsp] 29ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](a4-0-1.lsanca1-cr7.bbnplanet.net ok)
[nbsp]3 4.24.7.126[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp] 30ms[nbsp][nbsp] 31ms[nbsp][nbsp] 31ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](p0-0.lsanca2-br2.bbnplanet.net ok)
[nbsp]4 4.24.5.45[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]57ms[nbsp][nbsp] 34ms[nbsp][nbsp] 31ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](p15-0.lsanca2-br1.bbnplanet.net ok)
[nbsp]5 4.24.5.50[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]32ms[nbsp][nbsp] 30ms[nbsp][nbsp] 29ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](p7-0.lsanca1-br1.bbnplanet.net ok)
[nbsp]6 4.24.5.210[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp] 45ms[nbsp][nbsp] 47ms[nbsp][nbsp] 44ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](p7-3.paloalto-nbr2.bbnplanet.net ok)
[nbsp]7 4.0.6.78[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp] 45ms[nbsp][nbsp] 44ms[nbsp][nbsp] 44ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](p1-0.paloalto-cr2.bbnplanet.net ok)
[nbsp]8 192.205.32.145[nbsp][nbsp] 46ms[nbsp][nbsp] 53ms[nbsp][nbsp] 45ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](No rDNS)
[nbsp]9 12.123.13.66[nbsp][nbsp][nbsp][nbsp] 45ms[nbsp][nbsp] 47ms[nbsp][nbsp] 45ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](gbr3-p50.sffca.ip.att.net bogus rDNS: host not found [authoritative])
10 12.122.2.73[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]96ms[nbsp][nbsp] 96ms[nbsp][nbsp] 92ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](gbr3-p30.sl9mo.ip.att.net bogus rDNS: host not found [authoritative])
11 12.122.2.81[nbsp][nbsp][nbsp][nbsp] 110ms[nbsp][nbsp]109ms[nbsp][nbsp]110ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](gbr3-p20.wswdc.ip.att.net bogus rDNS: host not found [authoritative])
12 12.122.5.193[nbsp][nbsp][nbsp][nbsp]110ms[nbsp][nbsp]109ms[nbsp][nbsp]110ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](gbr5-p60.wswdc.ip.att.net bogus rDNS: host not found [authoritative])
13 12.123.9.57[nbsp][nbsp][nbsp][nbsp] 110ms[nbsp][nbsp]112ms[nbsp][nbsp]111ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](gar2-p360.wswdc.ip.att.net bogus rDNS: host not found [authoritative])
14 12.124.234.10[nbsp][nbsp] 114ms[nbsp][nbsp]114ms[nbsp][nbsp]114ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](No rDNS)
15 64.176.255.249[nbsp][nbsp]115ms[nbsp][nbsp]113ms[nbsp][nbsp]114ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](BGW-VE2.dedicatedns.com ok)
16 64.177.53.155[nbsp][nbsp] 114ms[nbsp][nbsp]114ms[nbsp][nbsp]116ms[nbsp][nbsp]TTL:239[nbsp][nbsp](kerrysherbals.com ok)
I've never seen a "bogus rDNS" before when I've done a traceroute. There is definitely something odd going on there?

Dean B
12-31-2000, 04:02 PM
No problems from the UK Mandi.

-Dean.

Jeff
12-31-2000, 04:11 PM
I've never seen a "bogus rDNS" before when I've done a traceroute. There is definitely something odd going on there?

Though I'm not sure when a "bogus rDNS" and when a "fradulent rDNS" is reported, these do not indicate a problem and seem to be getting more common.

For example:

Trace boatdesign.net (63.95.221.75) ...TTL:[nbsp][nbsp]0[nbsp][nbsp](ar-
[nbsp]5 137.39.130.105[nbsp][nbsp]234ms[nbsp][nbsp]219ms[nbsp][nbsp]219ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](37.atm1-0.alter.net bogus rDNS: host not found [authoritative])
[nbsp]8 146.188.138.178 234ms[nbsp][nbsp]234ms[nbsp][nbsp]203ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](106.at-7-0-0.tr2.dca8.alter.net bogus rDNS: host not found [authoritative])
[nbsp]9 152.63.144.50[nbsp][nbsp] 235ms[nbsp][nbsp]265ms[nbsp][nbsp]218ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](0.so-4-3-0.xr1.dca8.alter.net bogus rDNS: host not found [authoritative])
15 205.171.27.26[nbsp][nbsp] 297ms[nbsp][nbsp]266ms[nbsp][nbsp]282ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](tpa-edge-03.inet.qwest.net fraudulent rDNS)
16 63.144.0.106[nbsp][nbsp][nbsp][nbsp]297ms[nbsp][nbsp]312ms[nbsp][nbsp]281ms[nbsp][nbsp]TTL:[nbsp][nbsp]0[nbsp][nbsp](No rDNS)

[This message has been edited by Jeff (edited 12-31-00@3:11 pm)]

Mandi
01-01-2001, 01:11 AM
I have a client who is having trouble viewing her website via domainname, but can view via IP Address (not a FQ website).[nbsp][nbsp]Her ISP is DSL through her telco . . . in helping her troubleshoot, I was explaining about DNS refresh, blah blah blah.[nbsp][nbsp]Her ISP said, they don't use a DNS cache.[nbsp][nbsp]

Is that possible?[nbsp][nbsp]Sounds a bit like BS to me . . . ISP is insisting it "must" be her website, not them.[nbsp][nbsp]By the way, the rest of the world can view the website just fine.[nbsp][nbsp]Problem exists in both IE and NS.[nbsp][nbsp]Thanks for any insights into the inner workings of DSL, which I know nada about, thanks to absence of availability out here in the Gulf of Alaska.

Rich
01-01-2001, 01:46 AM
Mandi:

What is the domain name?
How long has it been registered?
Is she having trouble with http://domainname or http://www.domainname or both?

Rich

Terra
01-01-2001, 02:20 AM
Her ISP said, they don't use a DNS cache.[nbsp][nbsp]
Is that possible?[nbsp][nbsp]Sounds a bit like BS to me Yep, it's BS because if they are running DNS servers, then by nature they cache zone information until the TTL expires...[nbsp][nbsp]That is just the way it works - if they disbelieve then ask them if anyone has ever sat down and read the BOG manual...[nbsp][nbsp];)

Tsk Tsk Tsk, you are obviously dealing with an incompetent ISP that does not understand their own systems nor is willing to ask someone who does know...

Time to find someone who does...

--
Terra
--We know our systems because we built them from nothingness to something mystical--
FutureQuest

[This message has been edited by ccTech (edited 01-01-01@01:21 am)]

Mandi
01-01-2001, 04:16 PM
Thank you all :)![nbsp][nbsp]More details:

She also cannot access w/o the www part of the domain.

Webhost didn't change a thing (ie, NOC move or something.)

She spoke to someone who finally had heard of DNS cache (rolling my eyeballs) and confirmed they clear it at midnight.[nbsp][nbsp]Same tech also could not reach her site (silent cheer, glad I wasn't barking up the wrong tree.)

This morning, she still can't access.[nbsp][nbsp]I remember reading something (during a NOC move, I think) where we were cautioned about propagation, and not compounded the problem by checking "too soon" . . . the concept being, that DNS cacheing is relative to the user or something?[nbsp][nbsp]I am trying to caution her about this (in addition to encouraging a new ISP, LOL) and I'm mucking up the explanation . . . or am I remembering fairy dust, there??
[This message has been edited by Mandi (edited 01-01-01@3:21 pm)]

esc
01-12-2001, 02:48 AM
Hi Mandi,

The easiest thing for your client would be IMHO not to use the DNS-servers of the ISP at all. Though the access to DNS-servers can be restricted it is often not done. I for example use the servers of the local university that are connected to several main backbones and are set up correct. To speed up things further, put your client’s site into their host file which you will find in %systemroot%\system32\drivers\etc\ on NT and in a similar directory on the other MS Windows machines. Just search for ‘hosts’ on the boot drive. On Unixes it lives in the /etc directory and for Macs I don’t know. The syntax should be explained in the default hosts file.

The next thing you can do, case your client runs a local net with a Linux box in it, is to set this up as a caching, and forwarding-only DNS server. I have done it for our office and it’s quite simple, believe me. If you can set up Linux at all, you can do this too. The most complicated thing for me was to write the zone-files for the local net. But there are at least five HOWTOs that explain every step.

I’m on a Cable with flat rate myself which is overloaded in the afternoon and evening when people come home from work and school and start downloading mp3s, DVDs and warez. The local ping time rises then from a few milliseconds to about one second and more and the DNS queries sometimes time out.

If you have a Linux box in your net, you can watch the outgoing and returning DNS queries with

[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]tcpdump –i eth1 | grep domain

and optimize everything. For the other OSs there exist similar tools (packet sniffers).

Erich