FIX: Cannot Find Repo

Submitted by Tom Thorp on Friday, June 7, 2019 - 14:37
Modified on Friday, July 5, 2019 - 21:40

The Problem

In an ideal world, any domain name you query should be accessible on the internet, regardless of which resolver(s) you use to query the domain from. However what happens if the resolvers you normally rely on (eg. your ISP) aren't able to find the domain in question? Such is the case when I was using my ISP's resolvers to query the domain . 

Finding The Reason

I first set about finding the reason, by seeing if the domain was accessible on a device separate from my network. In this case, I chose my mobile to access the website via my cellular connection - in this case, successfully. I then tried accessing the website again, however this time through my home network. In this case, I wasn't able to access the website. From there, I knew it had to be a domain resolution issue with my home broadband. 
I next proceeded to change the domain name resolver on my home pc to a known external resolver - in this case I chose Google's resolvers & . As I expected, was able to be resolved. 
So what could make Google's resolvers able to resolve, but my ISP not? The answer lied in the primary and secondary name servers was delegated to. 
Doing a whois lookup on returns the delegation details of the following name servers :
When you do both a ping test and a dig test on the delegated name servers, yields the following results. 
[tom@GatewayFX ~]$ ping
ping: Name or service not known
[tom@GatewayFX ~]$ ping
ping: Name or service not known
[tom@GatewayFX ~]$ dig
dig: couldn't get address for '': not found
[tom@GatewayFX ~]$ dig
dig: couldn't get address for '': not found
So in essence, delegation details aren't properly configured. It's only that Google's name servers have cached the zone details of that the domain is visible on the internet.


There are two ways to work around this issue. It all depends on whether you have an internal DNS server as part of your network. 
1) No Internal DNS Server
If you have access to your DSL connection, change the resolver settings from what your ISP provided you, to known resolvers that will successfully query domain
2) Internal DNS Server
If you have an internal DNS server that's internet accessible, create a forward zone in your bind configuration that forwards any lookups to, to your nominated resolvers. eg. 
zone "" {
        type forward;
        forwarders {;; };
Once changed, test your config before restarting your DNS server.  
Hopefully this solution helps others who have been having repository configuration issues connecting to .

About the author

Tom Thorp
Tom Thorp is an IT Consultant living in Miami on Queensland's Gold Coast. With over 30+ years working in the IT industry, Tom's experience is a broad canvas. The IT services Tom provides to his clients, includes :
Website development and hosting
Database Administration
Server Administration (Windows, Linux, Apple)
PABX Hosting and Administration
Helpdesk Support (end-user & technical).
  If you like any of my content, consider a donation via Crypto by clicking on one of the payment methods :