How to resolve external domain names using MaraDNS in Windows 7

Question

I installed marades in a Windows 7 machine, I configured it, it can handle internal requests, but not external

marac file

ipv4_bind_addresses = "127.0.0.1" timestamp_type = 2 random_seed_file = "secret.txt" csv2 = {} csv2["myapp.com."] = "db.lan.txt" upstream_servers = {} # Initialize dictionary variable upstream_servers["."] = "8.8.8.8, 8.8.4.4" 

db.lan.txt

 private.% 192.168.1.21 ~ blog.% 192.168.1.16 ~ 

For external queries , this gives me the following error

 C:\Program Files\maradns-2-0-06-win32>askmara.exe Agoogle.com. # Querying the server with the IP 127.0.0.1 # Remote server said: REFUSED # NS replies: # AR replies: 

For internal requests, its operation is terminated, as shown below

 C:\Program Files\maradns-2-0-06-win32>askmara.exe Aprivate.myapp.com. # Querying the server with the IP 127.0.0.1 # Question: Aprivate.myapp.com. private.myapp.com. +86400 a 192.168.1.21 # NS replies: #myapp.com. +86400 ns synth-ip-7f000001.myapp.com. # AR replies: #synth-ip-7f000001.myapp.com. +86400 a 127.0.0.1 

And when I start the server,, I also get a warning prompt

How to solve this problem.

Answer 1

I had the same problem. This is fixed by replacing the latest version with version 1.4. after that, the only thing I did was run mkSecretTxt.exe to create the secret.txt file and configure the mararc file as follows:

this is my current mararc file:

 # Win32-specific MaraRC file; this makes a basic recursive DNS # server. hide_disclaimer = "YES" ipv4_bind_addresses = "127.0.0.1" recursive_acl = "127.0.0.1/8" timestamp_type = 2 csv2 = {} csv2["local.com."] = "db.lan.txt" # This is insecure until the secret.txt file is edited random_seed_file = "secret.txt" upstream_servers = {} upstream_servers["."] = "208.67.222.222,208.67.220.220" 

db.lan.txt

 % 192.168.1.33 ~ 

As you can see, I used openDNS servers, if you still get the error, try them as well. http://www.opendns.com/support/article/105

amuses

Answer 2

For those who follow this, it seems that the current solution from MaraDNS> 2.0 is to use MaraDNS with the included recursive Deadwood server in order to be able to handle both local and external resolution. I was able to get this to work on my Windows 10 computer with the following configurations ...

Suppose the IP address of a Windows device is 192.168.1.2

In the MaraDNS mararc file:

 ipv4_bind_addresses = "127.0.0.1" timestamp_type = 2 random_seed_file = "secret.txt" csv2 = {} csv2["mylocalnet.com."] = "db.lan.txt" 

In the db.lan.txt file:

 % 192.168.1.XXX ~ 

And in the Deadwood configuration file dwood3rc.txt :

 upstream_servers = {} upstream_servers["."]="8.8.8.8, 8.8.4.4" upstream_servers["mylocalnet.com."]="127.0.0.1" bind_address="192.168.1.2" recursive_acl = "127.0.0.1/16, 192.168.1.1/24" # By default, for security reasons, Deadwood does not allow IPs in the # 192.168.xx, 172.[16-31].xx, 10.xxx, 127.xxx, 169.254.xx, # 224.xxx, or 0.0.xx range. If using Deadwood to resolve names # on an internal network, uncomment the following line: filter_rfc1918 = 0 

You could configure several computers to work as independent servers, but my configuration above was special in that it allowed me to run both servers on the same computer. You can see that in the Deadwood configuration, I use Google’s DNS servers to handle all upstream requests, with the exception of mylocalnet.com. which is forwarded to localhost and handled by MaraDNS.

Here you just need to run both programs and point DNS to 192.168.1.2 . It must be good to go!