• July 15, 2025, 04:46:18 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DNS Issues  (Read 6381 times)

Teksonic

  • Level 1 Member
  • *
  • Posts: 4
DNS Issues
« on: February 18, 2009, 03:31:26 PM »

Hey all, just want to say thanks in advance for any help on this problem.

First, this is not a routing issue. No matter how I set this up I can get online no prob.  But i run a program called Kavoom (KM and KVM) and in one configuration they won't work across my network.

Setup is as such. (all machine's use static assigned IP's from 10.10.1.100 -> 10.10.1.111)
Mdm -> DIR 655 -> 100mb Switch -> 3 machine
                       -> NAS
                       -> 1 Machine
                       -> 1Gb Switch -> 3 machines

now when I use my ISP's DNS info and i ping any of those machine I will get a response from the local ip
Code: [Select]
Pinging phikmobile [10.10.1.106] with 32 bytes of data:

Reply from 10.10.1.106: bytes=32 time=1ms TTL=53
etc...

This will allow the Kavoom program to work as I'm guessing it's seeing the computer name based of it's local ip.

If I switch to OpenDns info and ping the same machine i get...

Code: [Select]
Pinging phikmobile.phub.net.cable.rogers.com [208.69.32.132] with 32 bytes of data:

Reply from 208.69.32.132: bytes=32 time=30ms TTL=53
etc..

Now because the opendns is now doing name resolution ???  my kavoom programs stop working across the whole network.

I have tried it with both the dns relay on and off, and i'm using the new beta firmware 1.22build11.

How can I stop the dir 655 from appending the domain name suffix and sending the requests out to open dns servers?
Logged

ttmcmurry

  • Level 4 Member
  • ****
  • Posts: 438
Re: DNS Issues
« Reply #1 on: February 18, 2009, 07:00:16 PM »

Lycan/EddieZ ... correct me if I'm wrong....

The DIR-655 is a Class-C networking router/switch.  Why are you using Class-A private IPs? 
Logged

lizzi555

  • Level 5 Member
  • *****
  • Posts: 605
Re: DNS Issues
« Reply #2 on: February 18, 2009, 08:36:03 PM »

You don't have any internal DNS resolution if you don't have installed a DNS-Server in your Homenet.
The internal Name resolution between Windows machines is done by the NetBIOS protocoll.

Try only with enabled DNS-relay. The OpenDNS servers only in in the WAN/Internet settings of the router.
All machines with static IP-adresses have to use the router ip as DNS server.

If this does not help try to use entries in the hosts. file for name resolution on the machine running Kavoom. This file is located in :

c:\windows\system32\drivers\etc\
You can use a normal text editor

Btw.: 10.10.1.x addresses should work if you set your subnetmask to 255.255.255.0
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: DNS Issues
« Reply #3 on: February 19, 2009, 01:58:00 AM »

Lycan/EddieZ ... correct me if I'm wrong....

The DIR-655 is a Class-C networking router/switch.  Why are you using Class-A private IPs? 

Using either class C or class A address spaces does not make any difference in this situation (see http://en.wikipedia.org/wiki/Private_network)
lizzi555 is making a very correct remark about the cause and solution.
Logged
DIR-655 H/W: A2 FW: 1.33

Teksonic

  • Level 1 Member
  • *
  • Posts: 4
Re: DNS Issues
« Reply #4 on: February 19, 2009, 12:49:00 PM »

Try only with enabled DNS-relay. The OpenDNS servers only in in the WAN/Internet settings of the router.
All machines with static IP-adresses have to use the router ip as DNS server.
Tried this before it has no effect.   Unless you mean to statically assign the routers ip into the DNS fields on the NIC's tcp/ip, which i just tried.  also to no avail.


If this does not help try to use entries in the hosts. file for name resolution on the machine running Kavoom. This file is located in :

c:\windows\system32\drivers\etc\
You can use a normal text editor

Btw.: 10.10.1.x addresses should work if you set your subnetmask to 255.255.255.0

I will try mapping the machines to there respective ip's in the host file and get back to you to see if it works.
« Last Edit: February 19, 2009, 12:52:19 PM by Teksonic »
Logged

Teksonic

  • Level 1 Member
  • *
  • Posts: 4
Re: DNS Issues
« Reply #5 on: February 19, 2009, 12:57:07 PM »

Mapping the netbios names into the host file corrected it.  Thank You for that suggestion.  I can finally use the OpenDNS servers.

 :D
Logged