Re: Resolver not always resolving hostnames
- From: Norikatsu Shigemura <nork@xxxxxxxxxxx>
- Date: Mon, 30 Oct 2006 00:08:36 +0900
On Sun, 29 Oct 2006 16:00:42 +0100
"Simon L. Nielsen" <simon@xxxxxxxxxxx> wrote:
When my latest cvsup failed this is the DNS packets captured:
15:06:45.036710 IP eddie.54684 > ns.nitro.dk.domain: 51917+ A? cvsup3.dk.freebsd.org. (39)
15:06:45.224002 IP ns.nitro.dk.domain > eddie.54684: 51917 0/0/0 (39)
15:06:45.224796 IP eddie.50804 > ns.nitro.dk.domain: 51918+ A? cvsup3.dk.freebsd.org.nitro.dk. (48)
15:06:45.226255 IP ns.nitro.dk.domain > eddie.50804: 51918 NXDomain* 0/1/0 (98)
We need the server side (= ns.nitro.dk) DNS query. hrs already
reported a behavier you said:-).
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- Re: Resolver not always resolving hostnames
- From: Jiawei Ye
- Re: Resolver not always resolving hostnames
- From: Hajimu UMEMOTO
- Re: Resolver not always resolving hostnames
- From: Jiawei Ye
- Re: Resolver not always resolving hostnames
- From: Hiroki Sato
- Re: Resolver not always resolving hostnames
- From: Simon L. Nielsen
- Re: Resolver not always resolving hostnames
- Prev by Date: EuroBSDCon is coming up !
- Next by Date: Re: Handling non-standard directories in tinybsd
- Previous by thread: Re: Resolver not always resolving hostnames
- Next by thread: Re: Resolver not always resolving hostnames
- Index(es):
Relevant Pages
|
|