[RADIATOR] Can Radiator Originate DNS Requests?

[Selim Tim]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20090312/383d1983/attachment.html>