When a client host requests information from a nameserver, it usually connects to port The nameserver then attempts to resolve the name requested. If it does not have an authoritative answer, or does not already have the answer cached from an earlier query, it queries other nameservers, called root nameservers , to determine which nameservers are authoritative for the name in question, and then queries them to get the requested name.
Nameserver Zones. The resource record is usually a fully qualified domain name FQDN of a host, and is broken down into multiple sections organized into a tree-like hierarchy. This hierarchy consists of a main trunk, primary branches, secondary branches, and so on. The following is an example of a resource record:. Each level of the hierarchy is divided by a period that is,.
In the example above, com defines the top-level domain , example its subdomain, and sales the subdomain of example. In this case, bob identifies a resource record that is part of the sales. With the exception of the part furthest to the left that is, bob , each of these sections is called a zone and defines a specific namespace.
Zones are defined on authoritative nameservers through the use of zone files , which contain definitions of the resource records in each zone. Zone files are stored on primary nameservers also called master nameservers , where changes are made to the files, and secondary nameservers also called slave nameservers , which receive zone definitions from the primary nameservers.
Both primary and secondary nameservers are authoritative for the zone and look the same to clients. Add your local network range. The example system uses IP addresses in the X range. This is specified as follows:. Specify a forward and reverse zone.
Zone files are simply text files that have the DNS information, such as IP addresses and host-names, on your system. The forward zone file makes it possible for the translation of a host-name to its IP address. The reverse zone file does the opposite. It allows a remote system to translate an IP address to the host name. The forward.
They can be called anything you like. Everything in bold is specific to your environment. Save the file and exit. Next, edit the reverse. Everything in bold is also specific to your environment. Look for your current name server line or lines.
Unfortunately there is one caveat to be aware of. But this gave me some ideas, I'll go rumble through the network-scripts , maybe it's there somewhere DravSloan I appreciate your ans, it works, but I have found some hack on google that I posted here.. The 1 worked for me, thanks a lot! On Debian Jessie at least, the file nm-system-settings. Nope, didn't help. It rewrote it anyway. As much as I could infer from that file, the plugins in that section are meant for caching of retrieved DNS records.
But I may be wrong. Did you restart the NetworkManager after editing the file? I disabled and enabled networking through the KDE widget. I believe that this should restart it. Unfortunately restarting it via service NetworkManager restart doesn't work - don't know why : it fails to connect after I try to restart it like this. Very strange that restart wouldn't work. I haven't experienced that in any of the systems that I've used.
It works. Show 1 more comment. PPPD senario Using ppon and ppoff probably means you are using pppd. From the pppd man page: usepeerdns Ask the peer for up to 2 DNS server addresses. Drav Sloan Drav Sloan Thanks, close, but not yet. The interface being used is ppp and there's no corresponding ifcfg-ppp file : — wvxvw.
How is your Point-to-Point connection being created? How was it configured? The interesting thing about it is that I do not know how it was created. My first guess was that it mus've been pppoeconf , but it isn't even installed here Updated to see if you can change it with pppd's settings.
0コメント