[nSLUG] resolving bellaliant.net while on fibreop

Stephen Yorke syorke at gmail.com
Thu Aug 20 11:06:30 ADT 2015


This works fine on my Debian 8 machine. I an on Eastlink business
internet, if that matters any.
From: Robert McKay
Sent: ‎2015-‎08-‎20 8:15 AM
To: nslug at nslug.ns.ca
Subject: Re: [nSLUG] resolving bellaliant.net while on fibreop
On 2015-08-20 03:15, D G Teed wrote:
> On Wed, Aug 19, 2015 at 7:29 PM, Robert McKay <robert at mckay.com>
> wrote:
> Tried with and without port 53...
[snip]
> # tcptraceroute -p 53 198.164.4.2
> traceroute to 198.164.4.2 (198.164.4.2), 30 hops max, 60 byte packets
>  1  router.asus.com (192.168.0.1)  0.318 ms  0.287 ms  0.256 ms
>  2  loop0.6cw.ba17.hlfx.ns.aliant.net (142.176.50.10)  8.929 ms
> 8.011 ms *
>  3  irb-84.cr02.hlfx.ns.aliant.net (142.176.53.49)  9.088 ms *
> 11.135 ms
>  4  * * *
>  5  * * *
>  6  * * *
>  7  * * *
> ... (to 30 hops)

The -p option to tcptraceroute sets the source port for the probes..
I think if you had instead used;

tcptraceroute 198.164.4.2 53

the results might have been different (with the traceroute completing).

> If I do the same trace to z3.eastlink.ca, the eastlink.ca DNS, it
> manages to get there in 12 hops.

Yes, but that's because eastlink's servers reply to UDP and ICMP probes
the
aliant servers do not.

> OK, I've found the problem.  Don't know why it is an issue, but
> things are fixed
> after a change on the router.  Your question caused me to search for
> the settings
> related to DNS on the router.  A setting on the WAN tab was called:
> "Connect to DNS Server automatically" and it had Yes selected.
> When this was unselected, two slots appeared for entering the DNS
> server IPs.  192.168.0.3 - my bind - was entered here and this was
> the only
> change applied.  Now sobeys.ca and bellaliant.net can be resolved.
> 192.168.0.1 was removed from resolv.conf and host lookups without
> specifying the DNS server are working for the trouble cases.
>
> Thanks for the troubleshooting questions, Robert  - it got me looking
> at the right aspect
> and this is now resolved (no pun intended).

Glad you got it working :)

Rob
_______________________________________________
nSLUG mailing list
nSLUG at nslug.ns.ca
http://nslug.ns.ca/mailman/listinfo/nslug


More information about the nSLUG mailing list