Stacey Marshall writes:
The master NS would only need to load the
root.zone file,
Other name servers within the private network would load the hint file.
That was it! The bogus DNS now does it's special
resolution like it should. Many thanks.
Martin McCormick
On 11 April 2011 14:04, Martin McCormick mar...@x.it.okstate.edu wrote:
Stacey Marshall writes:
I'm not certain as to what it is your trying to do exactly, but the hint
zone should provide addresses of root servers. One of which will be
contacted to download the list of root nameservers.
http://netreg.sourceforge.net/
The howto on that page has detailed setup for faked root.
Schilling
On Fri, Apr 8, 2011 at 10:58 AM, Martin McCormick
mar...@dc.cis.okstate.edu wrote:
I am trying to set up bind9.7.2P3 in a special manner such as is
used in network registration setups in which
On 11 April 2011 17:56, Stacey Marshall stacey.marsh...@gmail.com wrote:
On 11 April 2011 14:04, Martin McCormick mar...@x.it.okstate.edu wrote:
Stacey Marshall writes:
I'm not certain as to what it is your trying to do exactly, but the hint
zone should provide addresses of root servers.
I'm not certain as to what it is your trying to do exactly, but the hint
zone should provide addresses of root servers. One of which will be
contacted to download the list of root nameservers.
Wildcard address are really not very nice as they make resolver searches
ineffective when unexpected
I am trying to set up bind9.7.2P3 in a special manner such as is
used in network registration setups in which named always
returns the address of a registration server except for a few
other domains that supply updates and antivirus scans, etc.
In this case, I have microsoft.com as the
On Apr 8, 2011, at 10:58 AM, Martin McCormick wrote:
I am trying to set up bind9.7.2P3 in a special manner such as is
used in network registration setups in which named always
returns the address of a registration server except for a few
other domains that supply updates and antivirus scans,
John Wobus writes:
I think you want a *.com entry as well as the * entry.
I have now put in an entry like:
*.com. IN A 139.78.6.193
I still have the same behavior as before. The allowed
domain succeeds and all others get a SERVFAIL where they should
resolve to 139.78.2.193
8 matches
Mail list logo
