-
-
Even if the wildcard are not handled directly in Microsoft DNS server, they can be handled easly.
From the newsgroups:
1. Standard primary zone ( used to avoid going thru ldp or adsiedit to
modify AD zone info )
2. Create a temp host record.
3. right click server name and update data files.
4. stop DNS
5. Open the zonename.dns file in %systemroot%\system32\dns using notepad.
6. Modify the host name and change it to "*" without the quotes. ( MUST BE THE LAST RECORD TO PREVENT MISDIRECTION TO VALID HOSTS )
7 save file - restart DNS
Alternate solution use DNSCMD to create the record Syntax would be
"dnscmd /recordadd zonename * A IPADDRESS " ZoneName needs to be
replaced by the actual DNS zone name i.e. microsoft.com - IPADDRESS
would be replaced by the actual IP you want it to point to. This
should be the last record added to the zone - if it isn't remove it and
add any additional records then re-add when done.
-f.
-
-
Some issues with DCPromo, when removing a Domain controller:
I demoted a Domain Controller, and it's still in AD acting as a domain controller. To remove it, I found a walkthrough on Windows IT Pro that propose a solution, but even if the server was removed successfully I found another issue DSA object cannot be deleted.
The solution found on Microsoft, is to manually removed all related info in DNS, and use ADSIEdit.msc to delete the leaf.
After that I was able to re-add the demoted server as a member server in the domain.
-f.
-
-
After redeploying CRM 1.2, and upgrading it, I had problems using the CRM Installation, some pages were not migrated, and the customization neither.
I patched a few things manually (yeah :( ), and saw that the bizusers.srf was no longer working with the error "Server error loadlibrary failed". Like everybody knows, it's common to CRM that there'is no trace, so I queried my best friend Google to see various steps that may fix the problem.
The first one was to verify if the ISAPI crmisapi.dll was registered (using regsrvr32) and registered as the mapped ISAPI for the extension .srf. It was.
After that, verify if the .soap extension was registered to the .NET Framework. It was too.
Then, verify the content of the .srf file so that is "{{handler "C:\PROGRA~1\MICROS~2\Server\bin\CrmObjectModel.dll"/BizUser}}" and it was but it was not pointing to the good directory, it was Micros~3 and not Microso~2. That's why it was not working, I've copied the installated package from an other installation, that had other directories named Micros_ _ _ _ .
Why it's the juliet style path? Dunno. But now it's working.
After that I republished the customization, and now, everything works again.
-f.
-
-
A dynamic zone cannot be updated manually, to be able to do that, you must call "rndc freeze yourzone.com" then you can update the zone file, and after you must re-enable the zone by typing "rndc thaw yourzone.com".
... Guess what? Webmin can enable you RNDC, but does not send those commands when the zone is dynamic. G.
-f.
-
-
Ever wonder that 8min of open relay can be attacked by up to 1200 emails? Yeah, that's right, I wasn't.
Before proceding, I stopped the open relay by removing the firewall natted address from the internal network (I know.. I know). After that, I stopped the SMTP Server (If you don't all the in-memory queued email will be kept and retried later, even for NDR). Then, I deleted all Bad Mail, Queued, and Pick up, and restarted the SMTP Server.
-f.
-
-
I setupped Bind9 to be the one and only DNS Server in a Windows 2003 Active Directory environment, I forgot to disable SELinux when installing Fedora Core 4, and it must be disabled, recommended by the walkthrough of QMail Toaster... so I disabled it.
The only problem, is that when we disable SELinux, and update the Kernel after (yes, I've done that :S), all the configs a renamed to .rpmsave, the rnds.conf and named.conf too.
To solve the problem
rndc.key is only an included file of named.conf: Yes, that's it. You can copy the content of the file to named.conf.
rndc.conf is the configuration of rndc, it drives the show: This key must be copied to the named.conf file (or rndc.key) and all files must be concequent to each other.
-f.