[wellylug] Trouble resolving with name server
xavpaice at gmail.com
Mon Dec 18 09:07:04 UTC 2017
FWIW, it all works perfectly for me from Google's and Vodafone's DNS
servers, as well as querying freeparking direct. Can't see anything wrong,
but I'm not using the same ISP as you and their DNS rightly blocks my IP.
I'd be talking to your ISP, and getting it in writing from their tech that
they believe it's Freeparking's servers, and also be talking with
Freeparking and doing the same... then get some popcorn and watch the
battle. Most of the techs we get to speak with on the phone are only
really able to use a script, you'll want it escalated with pastebin type
evidence of the problem. I've not dealt with your ISP in years, but they
were great when I last did deal with them (before they were bought out).
My money's on the ISP's DNS doing something dumb, and there's a good chance
that they'll make another change, and either catastrophically fail or
accidentally fix this one while mopping up something seemingly unrelated.
On Mon, 18 Dec 2017 at 21:44 jumbophut <jumbophut at gmail.com> wrote:
> Hi all
> Hoping some of you strong in the ways of Linux-networking-fu will be
> able to help...
> My ISP (whom I won't name, though you could discover it without much
> effort) automatically assigns me two name servers when I my ASDL modem
> I try to resolve flo2cash.co.nz (the only site I am having trouble
> with; other websites are working) using each NS:
> $ nslookup flo2cash.co.nz 184.108.40.206 <- secondary
> $ nslookup flo2cash.co.nz 220.127.116.11 <- primary
> FAILS with "server can't find flo2cash.co.nz: SERVFAIL"
> $ dig flo2cash.co.nz @18.104.22.168
> FAILS with "SERVFAIL"
> This causes me difficulty (this is the site I use to pay domain name fees).
> To try and work out what is going on I also do:
> $ nslookup -norecurse flo2cash.co.nz 22.214.171.124
> FAILS with "Non-authoritative answer: *** Can't find flo2cash.co.nz: No
> $ dig +norecurse flo2cash.co.nz @126.96.36.199
> WORKS (but doesn't fix my problem because my web browser isn't as
> clever as dig).
> The explanation I have been given for why the primary NS doesn't work
> is that the authoritative servers for flo2cash.co.nz, which are
> ns.freeparking.co.nz and ns2.freeparking.co.nz, inexplicably bounce
> some requests (and apparently it's not confined to the NS I am having
> problems with).
> Does that sound right in the light of the results of nslookup / dig
> queries? It seems mighty strange that it works for one of the ISP's
> default name servers and not the other. Is there anything else I
> could do from my end to work out why it is failing?
> Note: the issue is solved by the workaround of using a couple of
> different name servers, but this doesn't seem to be fixing the
> underlying problem. It also requires reconfiguring my ASDL modem to
> _not_ use the NSs automatically assigned by the ISP's DHCP, and this
> leaves an untroubleshootable setup for less technologically inclined
> members of my household (e.g. if they do a factory reset of the modem
> for any reason and I am not home).
> Tony (echo 'spend!,pocket awide' | sed 'y/acdeikospntw!, /l at omcgtjuba.phi
> Wellington Linux Users Group Mailing List: wellylug at lists.wellylug.org.nz
> To Leave: http://lists.wellylug.org.nz/mailman/listinfo/wellylug
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wellylug