DNS entry anomaly

[bushdance]

Hi,

There is a discrepancy in a DNS entry between two TPG resolvers that is causing me grief.

The entry and its resolution by the two TPG resolvers are as follows:

C:\Users\peter>nslookup sso.jcu.edu.au 203.12.160.36
Server: dns2.tpgi.com.au
Address: 203.12.160.36

Non-authoritative answer:
Name: sso.glb.jcu.edu.au
Address: 137.219.21.55
Aliases: sso.jcu.edu.au

C:\Users\peter>nslookup sso.jcu.edu.au 203.12.160.35
Server: dns1.tpgi.com.au
Address: 203.12.160.35

Name: sso.jcu.edu.au

C:\Users\peter>

My TPG PPPoE defaults dictate the use of dns1.tpgi.com.au as the primary resolver, which fails to resolve sso.jcu.edu.au. I've worked around it by forcing an override of my local DNS settings to query dns2.tpgi.com.au first instead --- but would definitely appreciate the DNS entries be consistent across both members please, rather than relying on my workaround. Just pointing it out for your attention.

Many thanks & regards

Peter

[BasilDV]

Hi @bushdance

Welcome to the Community!

We'd like to look into your account for better understanding of the situation and arrange a call from our Tech team to check on this further.

Please send me a PM with your TPG username or customer ID number.

BasilDV

[bushdance · Accepted solution]

Hi BasilDV,

Thanks for your response. I hope this was the right channel for reporting this kind of anomaly. At the time, I couldn't find any other means of lodging a technical enquiry, unfortunately.

The problem was ultimately resolved yesterday.

dns1.tpgi.com.au started resolving sso.jcu.edu.au (an alias of sso.glb.jcu.edu.au) correctly with 137.219.21.55 once more, same as dns2.tpgi.com.au. So, I was satisfied to revert a workaround that I had set up for myself.

I don't believe it was an isolated situation with just my account though.

The issue was a discrepancy with the DNS record between the two DNS members.

dns2.tpgi.com.au was seemingly fine, reporting the same result as 8.8.8.8.

I had at least one other user, an iiNet client, experience the same issue.

I assisted her with a workaround to get her going again temporarily.

In any case, happy to provide my username if you would like a cursory look anyway: xxxxx

Thanks & regards

Peter

[Anonymous]

Hi @bushdance,

I am glad to know that the issue has been resolved yesterday, feel free to create a new thread for any concern in the future, cheers!

Hi BasilDV,

Thanks for your response. I hope this was the right channel for reporting this kind of anomaly. At the time, I couldn't find any other means of lodging a technical enquiry, unfortunately.

The problem was ultimately resolved yesterday.

dns1.tpgi.com.au started resolving sso.jcu.edu.au (an alias of sso.glb.jcu.edu.au) correctly with 137.219.21.55 once more, same as dns2.tpgi.com.au. So, I was satisfied to revert a workaround that I had set up for myself.

I don't believe it was an isolated situation with just my account though.

The issue was a discrepancy with the DNS record between the two DNS members.

dns2.tpgi.com.au was seemingly fine, reporting the same result as 8.8.8.8.

I had at least one other user, an iiNet client, experience the same issue.

I assisted her with a workaround to get her going again temporarily.

In any case, happy to provide my username if you would like a cursory look anyway: xxxxx

Thanks & regards

Peter