[RADIATOR] Can Radiator Originate DNS Requests?

[Hugh Irvine]

Hello Tim -

I will need to see a copy of the Radiator configuration file and a  
trace 4 debug showing what is happening.

You can also run wireshark (aka ethereal) or tcpdump on the Radiator  
host to see what packets are sent/received.

regards

Hugh


On 12 Mar 2009, at 23:31, Selim Tim wrote:

> Hi,
>
> Sorry if this is a dumb question.
>
> We're using Radiator 3.17 on Sun T1000s/Solaris 10, with an Oracle  
> IP allocation database.
>
> When a request is handled that requires an IP allocation from a full  
> or non-existent, we have Radiator set up to log 'NO_IP' as the fail  
> code in our auth logfiles.
>
> When 'NO_IP' auth events are logged, we are seeing DNS requests  
> being sent from our Radiator app servers and are trying to work out  
> why
>
> Here's an example, snipped from a local firewall log -
>
> 13:22:45.067097 193.113.200.200.domain > 192.168.63.50.42509:  55048  
> NXDomain q: A? RAD3PS1. 0/1/0 ns: . SOA[|domain] (DF) (ttl 255, id  
> 52304, len 128)
>
> 13:22:45.067269 193.113.200.200.domain > 192.168.63.50.42509:  55048  
> NXDomain q: A? RAD3PS1. 0/1/0 ns: . SOA[|domain] (DF) (ttl 254, id  
> 52304, len 128)
>
> 13:22:46.111757 193.113.200.200.domain > 192.168.63.50.42510:  36206  
> NXDomain* q: A? NO_IP.london.02.net. 0/1/0 ns: london.02.net. SOA[| 
> domain] (DF) (ttl 255, id 52305, len 117)
>
> 13:22:46.111952 193.113.200.200.domain > 192.168.63.50.42510:  36206  
> NXDomain* q: A? NO_IP.london.02.net. 0/1/0 ns: london.02.net. SOA[| 
> domain] (DF) (ttl
>
> 192.168.63.50 isn't actually bound to a radiusd process, but it is  
> the front end physical interface for one our Radiator servers.
>
> It suggests that the server wants to send some sort of message  
> triggered by the NO_IP event, but I can't find anything in our  
> Radiator configs to hint at why this should happen.  Our unix admins  
> have looked on the servers (including the perl modules Radiator  
> uses) but haven't found anything either.  Maybe we haven't looked  
> closely enough.
>
> So, can you please suggest any circumstances under which Radiator  
> (or one of perl modules that supports it) might send DNS requests?
>
> Thanks
>
> Tim
>
> Tim Selim Data Access Designer
>
> Telefónica O2 UK Limited
>
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
Have you checked the RadiusExpert wiki:
http://www.open.com.au/wiki/index.php/Main_Page

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.