[OT] name resolution... ( was Re: FreeBSD Traffic Shaping )

[Norberto Meijome]

On Thu, 03 Apr 2008 15:55:05 +1100
Terry Sposato <terry at sucked-in.com> wrote:

> Norberto Meijome wrote:
> > On Wed, 2 Apr 2008 14:43:20 +0200
> > Mel <fbsd.questions at rachie.is-a-geek.net> wrote:
> > 
> >> I think you'll find that bursts are best counteracted like this:
> >> http://www.probsd.net/pf/index.php/Hednod%27s_HFSC_explained#Tips.2FIdeas
> > 
> > Mel, can you please confirm this link / FQDN ? no NS defined for the domain... 
> > 
> > TIA,
> > B
> <SNIP>
> 
> The above link works fine for me here.
> [terry at got ~]$ host www.probsd.net
> www.probsd.net has address 66.93.16.108
> 

i hear you :D 

It resolves ok when pointing against a US based Name server :

$ nslookup www.probsd.net ns1.octantis.com.au
Server:         ns1.octantis.com.au
Address:        207.44.188.147#53

Non-authoritative answer:
Name:   www.probsd.net
Address: 66.93.16.108

It doesn't work when using my machine's named, which relies on Root name servers to get the info. the US server also uses root servers for resolution.

US box is linux based, mine is FBSD 7, in AU.

I checked with wireshark and i never get any reply from their servers. they seem to reply if I use my ISP's dns... 

oh well


_________________________
{Beto|Norberto|Numard} Meijome

"The only good bureaucrat is one with a pistol at his head.
Put it in his hand and it's goodbye to the Bill of Rights."
   H.L. Mencken

I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.