[Snap] Accessing/resolving .nz TLD's from Snap connection

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] Accessing/resolving .nz TLD's from Snap connection

Aaroona

3196 posts

Uber Geek

#170975 1-Apr-2015 09:42

has anyone had an issue with this?

I don't have any other .nz TLD's to try, but I registered a new one yesterday, and it works from every connection, except any device connected to my Snap VDSL connection... Very strange.

1 | 2

162 posts

Master Geek

#1274998 1-Apr-2015 10:21

I have a .nz and .uk, both work fine over my Snap DSL, I'm using 202.37.101.1 and 202.37.101.2 as my resolvers

Peppery

919 posts

Ultimate Geek

Trusted

#1275030 1-Apr-2015 10:31

How long since registration did you try access it? If you try visit it before it's fully resolved then Snap may be caching the DNS response. You'll simply have to wait in this instance.

Aaroona

3196 posts

Uber Geek

#1275032 1-Apr-2015 10:34

wjw: I have a .nz and .uk, both work fine over my Snap DSL, I'm using 202.37.101.1 and 202.37.101.2 as my resolvers

Such a weird issue. I am also using those DNS servers as my resolvers.

Peppery: How long since registration did you try access it? If you try visit it before it's fully resolved then Snap may be caching the DNS response. You'll simply have to wait in this instance.

That's what I'm kind of thinking, but, I wonder what their TTL is? Because EVERY service I have used thus far (email hosts, Telstra Clear DSL, Vodafone 3G/4G, online services) all report it being online and can access the landing page.
It was activated last night around 5-6pm, and I swapped NS records to Cloudflare and all the services could see it within an hour.

wjw

162 posts

Master Geek

#1275039 1-Apr-2015 10:37

trying pinging mx1.wjw.nz

timmmay

20587 posts

Uber Geek

Trusted

Lifetime subscriber

#1275044 1-Apr-2015 10:39

I have a .nz domain that works on my snap fiber.

Aaroona

3196 posts

Uber Geek

#1275046 1-Apr-2015 10:41

wjw: trying pinging mx1.wjw.nz

Okay, so that pings, no issues.

Must be a DNS propagation issue. Weird, Snap are usually on the ball with DNS - any changes I've made in the past have all been active on Snap before anywhere else... this time the complete reverse...

What is the normal wait time? (recommended?) was it 24 hours? or 72 for DNS? I can't remember.

Peppery

919 posts

Ultimate Geek

Trusted

#1275067 1-Apr-2015 10:53

I'd give it at least 24 hours.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

wjw

162 posts

Master Geek

#1275068 1-Apr-2015 10:53

have you tried doing a manual nslookup? see if it produces an error?

Aaroona

3196 posts

Uber Geek

#1275074 1-Apr-2015 10:55

wjw: have you tried doing a manual nslookup? see if it produces an error?

Yeah, immediately comes back with an error, saying that no A or AAAA records were available, and on OpenWRT (directly on the router), it says Name or service not known.

Aaroona

3196 posts

Uber Geek

#1275118 1-Apr-2015 11:32

I can confirm that Snap is still pointing to the old name servers.

I just added an A record under using the DNS manager through the site I registered the domain with, and that record is now active and pinging from my connection... so just have to wait for the NS records to update... Weirdly though, if i send the email via Snap's webmail, to my new domain, it does arrive.

Aaroona

3196 posts

Uber Geek

#1276867 3-Apr-2015 19:19

It looks like Snap have a different DNS refresh threshold when it comes to .nz TLDs.

My .nz finally updated, after a FULL 24 hours, and now I've made another DNS change, it is taking forever again.

I tested a DNS update on my .com address, and it went through within a matter of minutes...

I might log a call to see at least why this is up, unless Ralph is around here somewhere?

sorceror

163 posts

Master Geek

#1276902 3-Apr-2015 21:03

instead of calling support you should do some reading - it's impossible for a DNS server to treat certain TLDs differently, that's just not how the system works.

what would've happened is that the Snap server would've cached the NS record for your domain from one of the nsX.dns.net.nz servers which are authoritative for the .NZ zone - the default TTL on these records is 86400 seconds (24 hours).

Aaroona

3196 posts

Uber Geek

#1276908 3-Apr-2015 21:15

sorceror: instead of calling support you should do some reading - it's impossible for a DNS server to treat certain TLDs differently, that's just not how the system works.

what would've happened is that the Snap server would've cached the NS record for your domain from one of the nsX.dns.net.nz servers which are authoritative for the .NZ zone - the default TTL on these records is 86400 seconds (24 hours).

So I understand this correctly- The TTL for the .NZ zone is 84600, controlled by dns.net.nz? So then it's pointless me having a different TTL on my records, say 60 minutes, as the authoritative server TTL will take priority?

I will go do some reading shortly.

sorceror

163 posts

Master Geek

#1276910 3-Apr-2015 21:18

the dns.net.nz servers only really hold NS records. so the long TTL would only apply if you are changing the NS record for the entire domain at the registrar - this shouldn't be something that you do often.

you can still have low TTL's for all other records - these queries go to your nominated name server and not the dns.net.nz servers so you have full control

Aaroona

3196 posts

Uber Geek

#1276914 3-Apr-2015 21:27

sorceror: that's only if you're changing the NS record for the entire domain at the registrar - this shouldn't be something that you do often.

you can still have low TTL's for A records MX records etc

That's where I'm having issue understanding what you're trying to explain.

I changed my NS servers for my domain to cloudflare the other day (all my domains DNS are hosted here)... that all seem to be fine. Cloudflare records, if left to the default settings for TTL, is set to 5 minutes (not good practice, I know).

So to make sure I'm understanding this properly, wouldn't DNS work something like this:

Query test.domain.com > Snap DNS doesn't resolve from cache.. at this point, would it not hand the query down the line until it reaches my NS server, which would then resolve my new record, passing that response down the line back to me?

Just in case there is any confusion in what I've terribly explained, what I'm getting at is.. my records (lets say A records) are not becoming active as quick on my .nz domain as my A records on my .com domain.

Edit: worth mentioning, Originally I was talking about the NS update, which your reply would have made sense with.. but now I'm talking about records within my zone, now that the NS records are updated :)

1 | 2