MSGID: 1:229/426 BCACA467
On 16 Mar 19  12:42:34, Ward Dossche said the following to Terry Roati:

WD> Next, before I move/change anything I need someone to explain to me what th
WD> functionality of these lines is:
WD>  
WD>    Name Server: NS.BOFH.IT
WD>    Name Server: NS.FIDONET.ORG.UA

These are the addresses of the servers that host the DNS records for the 
domain. As it stands, you have control of the fidonet.org domain but you do 
not have control over the DNS records.

The last time I looked at it, there were hundreds of records, most related to
Region 50 and gating Internet email. There is a Perl script that runs on 
Bofh.it which supposedly "sync's up" this with the current Nodelist. That 
script is what is actually generating the DNS records for BIND. My 
understanding is that it is not possible to directly edit the records.

Region 50 is effectively acting as their own collective Internet Email
provider and the gating is askin to the old days of the IEEE gateway.

I have fidonet.org's script and DNS records Marco sent me in a backup here... 
I can look at it more in detail next week.

The last conversation I had with Macro was that the domain is extremely
high-traffic with the amount of DNS queries, Email to Region 50 and overall 
spam/script attacks. There is absolutely no way that someone can just host 
this domain on a home server for example. You need a more robust host for 
this... and remember what I said about "trust".

A correct solution is to have at least two virtual-machines set up through a 
cheap cloud company - OVH out of Montreal Quebec for example - as the Name
Servers and one that runs the Perl script to generate DNS for BIND.  This
will at least ensure no downtime or complaints and completely eliminate the
existing situation with Marco and the Italians... until this setup with Region
50 can be looked at further.

Now lets cue to the know-it-alls.

Nick

--- Renegade vY2Ka2