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 RPMFusion.org .
Finding The Reason
I first set about finding the reason, by seeing if the RPMFusion.org 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 RPMFusion.org 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 8.8.8.8 & 8.8.4.4 . As I expected, RPMFusion.org was able to be resolved.
So what could make Google's resolvers able to resolve RPMFusion.org, but my ISP not? The answer lied in the primary and secondary name servers RPMFusion.org was delegated to.
Doing a whois lookup on RPMFusion.org returns the delegation details of the following name servers :
Name Server: NSSEC.ONLINE.NET
Name Server: NS1.RPMFUSION.NET
When you do both a ping test and a dig test on the delegated name servers, yields the following results.
[tom@GatewayFX ~]$ ping nssec.online.net
ping: nssec.online.net: Name or service not known
[tom@GatewayFX ~]$ ping ns1.rpmfusion.net
ping: ns1.rpmfusion.net: Name or service not known
[tom@GatewayFX ~]$ dig @nssec.online.net rpmfusion.org
dig: couldn't get address for 'nssec.online.net': not found
[tom@GatewayFX ~]$ dig @ns1.rpmfusion.net rpmfusion.org
dig: couldn't get address for 'ns1.rpmfusion.net': not found
So in essence, RPMFusion.org delegation details aren't properly configured. It's only that Google's name servers have cached the zone details of RPMFusion.org that the domain is visible on the internet.
Solution
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 RPMFusion.org 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 RPMFusion.org, to your nominated resolvers. eg.
zone "rpmfusion.org" {
type forward;
forwarders { 8.8.8.8; 8.8.4.4; };
};
Once changed, test your config before restarting your DNS server.
Hopefully this solution helps others who have been having repository configuration issues connecting to RPMFusion.org .
About the author |
|
 |
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 :
|
|
